CN115148322A

CN115148322A - Clinical data storage method and system of clinical medical universal data structure model

Info

Publication number: CN115148322A
Application number: CN202211063029.5A
Authority: CN
Inventors: 王强; 李超; 孙汉清
Original assignee: Digital Health China Technologies Co Ltd
Current assignee: Digital Health China Technologies Co Ltd
Priority date: 2022-08-31
Filing date: 2022-08-31
Publication date: 2022-10-04

Abstract

The invention relates to the technical field of hospital data storage, in particular to a clinical data storage method and a system of a clinical medical general data structure model, wherein the method comprises the steps of extracting multi-modal clinical relevant data, storing the multi-modal clinical relevant data in different information blocks of the clinical medical general data structure model in a classified manner, setting one or more information tables in each clinical data information block, at least setting a patient ID and a treatment ID in one information table, associating all information tables related to the clinical medical general data structure model through the patient ID and the treatment ID, and integrating to obtain the relevant data of a patient; according to the invention, the clinical relevant data is classified and stored, so that the patient information is comprehensively inquired through the patient ID, and the correlation is carried out through the relevant fields, so that the different classified data have the relation, and the correlation acquisition is realized.

Description

Clinical data storage method and system of clinical medical universal data structure model

Technical Field

The invention relates to the technical field of hospital data storage, in particular to a clinical data storage method and system of a clinical medical general data structure model.

Background

In recent years, computer technologies such as artificial intelligence, natural language processing, data mining and the like are rapidly developed, however, at present, the structuralization of medical data is still in a lower level, more medical data still appears in a natural language text form, and the learning capacity of natural people is limited, so that students continuously try to complete the process of summarizing knowledge in the medical field by assistance of computer technology, refine the knowledge, extract useful diagnosis and treatment information in the knowledge, and finally form a knowledge body or a knowledge network, so that standards and convenience are provided for various subsequent text mining tasks.

Disclosure of Invention

In view of the above deficiencies of the prior art, the present invention aims to provide a multi-modal clinical data storage method and system based on a clinical medical general data structure model, so as to solve the problems of low relevance of hospital information data, incomplete query, redundant data storage and space waste.

In order to solve the problems, the invention adopts the following technical scheme:

in a first aspect, the present invention provides a method for storing clinical data of a clinical medical universal data structure model, including:

extracting multi-modal clinically relevant data;

storing the multi-modal clinically relevant data in different information blocks of a clinical medical general data structure model in a classified manner, wherein the information blocks comprise clinical data information blocks;

setting one or more information tables in each clinical data information block;

setting a patient ID and a visit ID in at least one information table, using the patient ID as an identifier of a patient in the clinical medical universal data structure model, associating the information tables related to the patient ID in the clinical medical universal data structure model through the patient ID, and integrating all data of the patient in the clinical medical universal data structure model; and using the visit ID as a single visit identification of the patient in the clinical medical general data structure model, associating all information tables related to the visit ID in the clinical medical general data structure model through the visit ID, integrating to obtain all data of the patient in the single visit, further setting an interface table main key ID corresponding to the information table in the information table, and associating the original data of the information table through the interface table main key ID.

Further, the extracting clinically relevant data for multiple modalities includes: the multi-modal clinical relevant data is extracted by natural language processing technology.

Further, the multi-modal clinically relevant data includes HIS, LIS, EMR, imagery, pathology, genetic and natural language processing information.

Further, the multi-modal clinically relevant data is derived from oracle, mysql, sql server and/or hbase databases.

In a second aspect, the invention provides a clinical data storage system of a clinical medical general data structure model, which comprises a clinical relevant data extraction module, a data storage module, an information table setting module and an information association module;

the clinical relevant data extraction module is used for extracting multi-modal clinical relevant data;

the data storage module is used for storing the multi-modal clinical relevant data in different information blocks of a clinical medical general data structure model in a classified manner, and the information blocks comprise clinical data information blocks;

the information table setting module is used for setting one or more information tables in each clinical data information block;

the information association module is used for at least setting a patient ID and a visit ID in the information table, using the patient ID as the identification of the patient in the clinical medical general data structure model, associating the information table related to the patient ID in the clinical medical general data structure model through the patient ID, and integrating all data of the patient in all clinical medical general data structure models; and using the visit ID as a single visit identification of the patient in the clinical medical general data structure model, associating all information tables related to the visit ID in the clinical medical general data structure model through the visit ID, integrating to obtain all data of the patient in the single visit, further setting an interface table main key ID corresponding to the information table in the information table, and associating the original data of the information table through the interface table main key ID.

Further, in the clinical relevant data extraction module, multi-modal clinical relevant data is extracted through a natural language processing technology.

In a third aspect, the invention further provides a clinical medical data query method, based on the clinical data storage system of the clinical medical universal data structure model, querying all data of the patient in the clinical data storage system of the clinical medical universal data structure model through the patient ID.

Specifically, the querying all data of the patient in the clinical data storage system of the clinical medical universal data structure model through the patient ID includes:

inputting the patient ID;

finding one or more information tables with the same patient ID from all the information tables;

and if a plurality of information tables exist, removing the same information in the information tables, retaining different information, and integrating all data of the patient in the clinical data storage system of the clinical medical universal data structure model according to the different information.

Further, all data of the patient in a single visit in the clinical data storage system of the clinical medical universal data structure model of the patient are inquired through the visit ID.

Specifically, the querying, by the visit ID, all data of the patient at a single visit in the clinical data storage system of the clinical medical universal data structure model includes:

inputting the visit ID;

finding out one or more information tables with the same clinic ID from all the information tables;

and if a plurality of information tables exist, removing the same information in the information tables, reserving different information, and integrating all data of the patient in a single visit in the clinical data storage system of the clinical medical general data structure model according to the different information.

In a fourth aspect, the invention provides a clinical medical data query system, which is a clinical data storage system based on the clinical medical universal data structure model and further comprises a patient all-data query module;

and the patient all-data query module is used for querying all data of the patient in the clinical data storage system of the clinical medical universal data structure model through the patient ID.

Specifically, the patient data query module comprises an input unit, an information table lookup unit and a data integration unit;

the input unit is used for inputting the patient ID;

the information table searching unit is used for finding out one or more information tables with the same patient ID from all the information tables;

the data integration unit is used for removing the same information in the information tables and reserving different information if a plurality of information tables exist, and integrating all data of the patient in the clinical data storage system of the clinical medical general data structure model according to the different information.

Further, the system also comprises a patient single-visit data query module;

and the patient single-visit data query module is used for querying all data of the patient in a single visit in the clinical data storage system of the clinical medical general data structure model through the visit ID.

Specifically, the patient single-visit data query module comprises an input unit, an information table lookup unit and a data integration unit;

the input unit is used for inputting the visit ID;

the information table searching unit is used for searching one or more information tables with the same treatment ID from all the information tables;

the data integration unit is used for removing the same information in the information tables and reserving different information if a plurality of information tables exist, and integrating all data of the patient in a single visit in the clinical data storage system of the clinical medical general data structure model according to the different information.

The invention has the beneficial effects that: according to the clinical data storage method and system of the clinical medical general data structure model, comprehensive inquiry and tracing of patient information are achieved through patient ID by classifying and storing clinically relevant multi-modal data, and correlation is achieved through relevant fields, so that different classified data are associated, and correlation acquisition is achieved; and the generic data structure model can support comprehensive, systematic storage of clinical data that accommodates multiple modalities; the data tables can be effectively associated based on the ID, the table-based association can be used for effective query retrieval and tracing, and combined query is supported; and the data structure of the generic model may be compatible with the mainstream database.

Drawings

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings, in which:

fig. 1 is a flow chart illustrating a method for storing clinical data of a clinical medical universal data structure model according to an embodiment of the present invention.

FIG. 2 is a diagram of a clinical data storage system of a clinical medical generic data structure model according to an embodiment of the present invention.

Fig. 3 is a flowchart illustrating a method for querying clinical medical data according to an embodiment of the present invention.

Fig. 4 is a schematic diagram of a clinical medical data query system according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to specific examples.

It should be noted that these examples are only for illustrating the present invention, and not for limiting the present invention, and the simple modification of the method based on the idea of the present invention is within the protection scope of the present invention.

Referring to fig. 1, a method for storing clinical data of a clinical medical universal data structure model includes:

s100, extracting multi-modal clinical relevant data;

s200, storing the multi-modal clinical relevant data in different information blocks of a clinical medical general data structure model in a classified manner, wherein the information blocks comprise clinical data information blocks;

s300, setting one or more information tables in each clinical data information block;

s400, setting a patient ID and a visit ID in at least one information table in the information tables, using the patient ID as the identification of the patient in the clinical medical general data structure model, associating the information tables related to the patient ID in the clinical medical general data structure model through the patient ID, and integrating to obtain all data of the patient in the clinical medical general data structure model; and using the visit ID as a single visit identification of the patient in the clinical medical general data structure model, associating all information tables related to the visit ID in the clinical medical general data structure model through the visit ID, integrating to obtain all data of the patient in the single visit, further setting an interface table main key ID corresponding to the information table in the information table, and associating the original data of the information table through the interface table main key ID.

As an embodiment, the extracting the clinically relevant data of the multiple modalities includes: the multi-modal clinical relevant data is extracted by natural language processing technology.

As an embodiment, the multi-modal clinically relevant data includes HIS, LIS, EMR, imagery, pathology, genetic and natural language processing information.

As an embodiment, the multi-modal clinically relevant data is derived from oracle, mysql, sql server and/or hbase databases.

As an implementable embodiment, the clinical data information block comprises a text record block;

the text recording block comprises a text recording information table, a natural language processing information table and a hospital admission recording information table;

the text record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the text editing time, a field 5 which is the text type, a field 6 which is the text content and a field 7 which is the interface table main key ID;

the admission record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the recording time and a field 5 which is the interface table main key ID;

the natural language processing information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is an external key of the natural language processing information table, a field 3 which is a processing date, a field 4 which is a paragraph name of data from an original text, a field 5 which is a text window of data, a field 6 which is a character offset of the data in the whole text, a field 7 which is a main key ID of an interface table, a field 8 which is a standard concept name of the original text after standardized processing, a field 9 which is a name and a version of an NLP system for extracting the term, a field 10 which is a relation attribute value of the field 7, and a field 11 which is a relation attribute type of the field 10 and the field 7;

and determining which section of the text the named entity or relationship obtained after natural language processing comes from, and the position of a part of word content around the named entity and the named entity in the whole text through the field 2, the field 4, the field 5, the field 6 and the field 7 in the natural language processing information table.

As an implementable embodiment, the clinical data information block includes a surgical examination information block;

the operation examination information block comprises an examination information table, an image sequence example information table and an image omics information table;

the examination information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the examination name, a field 5 which is the examination category, a field 6 which is the examination time, a field 7 which is the report time, a field 8 which is the objective result of the examination report, a field 9 which is the subjective result of the examination report and a field 10 which is the primary key ID of the interface table;

the image sequence information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is a related examination ID, a field 3 which is a patient ID, a field 4 which is a clinic ID and a field 5 which is a main key ID of an interface table;

the image sequence example information table comprises a unique identification ID with a field 1 as the table and a primary key ID with a field 2 as the interface table;

the imaging omics information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the main key associated with the influence sequence example table and a field 5 which is the interface table main key ID.

As an implementation manner, the image sequence information table further includes that byte 6 is DICOM generation date, byte 7 is serial number, byte 8 is layer thickness, byte 9 is position, byte 10 is window level, byte 11 is window width, byte 12 is line resolution, byte 13 is column resolution, byte 14 is position, byte 15 is slope, and byte 16 is sequence set file directory;

the video sequence instance information table further includes byte 3 as instance Num, byte 4 as storing chat path, byte 5 as relative path, byte 6 as check ID, byte 7 as sequence ID and byte 8 as SOP instance ID;

the image omics information table also comprises a group byte 6 as the name of the omic characteristics and a byte 7 as the result of the omic characteristics.

As an implementable embodiment, the clinical data information block includes at least one of a registration record block, a visit information block, a diagnosis information block, a prescription order information block, a test information block, a surgical procedure information block, an examination information block, a pathology specimen information block, a care information block, a text record block, a cost record block, a radiotherapy record block, a chemotherapy record block, a cancer pain treatment block, an instrument use record block, and a pathology information block;

the registration recording block comprises a registration recording information table; the registration record information table comprises a registration ID (identification) field 1, a patient ID field 2, a main key ID field 3 and a treatment ID field 4, wherein the registration ID field 1 is a registration ID, the patient ID field 2 is a patient ID, and the treatment ID field 4 is an interface table;

the treatment information block comprises a treatment information table, wherein the treatment information table comprises a field 1 of treatment ID, a field 2 of patient ID, a field 3 of treatment type, a field 4 of interface table main key ID, a field 5 of treatment type original value and a field 6 of treatment starting time;

the diagnosis information block comprises a diagnosis information table, wherein the diagnosis information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is a patient ID, a field 3 which is a diagnosis ID, a field 4 which is a diagnosis start time, a field 5 which is a diagnosis original name, a field 6 which is a main key ID of an interface table, a field 7 which is a diagnosis code, a field 8 which is a diagnosis standardized name and a field 9 which is a diagnosis type;

the prescription medical advice information block comprises a medication information table and a non-medication type prescription medical advice information table;

the medication information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the medicine name, a field 5 which is the start time, a field 6 which is the end time, a field 7 which is the original name of the medicine, a field 8 which is the main key ID of the interface table and a field 9 which is the medicine type;

the non-medication prescription medical advice information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is a patient ID, a field 3 which is a treatment ID, a field 4 which is a main key ID of an interface table, a field 5 which is an item name of medical advice and a field 6 which is start time;

the test information block comprises a laboratory test information table and a microorganism test information table;

the laboratory test information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the name of a detection small item, a field 5 which is the detection time, a field 6 which is the original name of the detection small item, a field 7 which is the main key ID of an interface table and a field 8 which is the original value of the test result;

the microbial detection information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the item number, a field 5 which is the instrument number, a field 6 which is the colony number and a field 7 which is the main key ID of an interface table;

the operation information block comprises an operation information table; the operation information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the diagnosis ID, a field 4 which is the operation name, a field 5 which is the operation standardized name, a field 6 which is the operation starting time, a field 7 which is the operation name of the operation interface table and a field 8 which is the main key ID of the interface table;

the pathological specimen information block comprises a pathological specimen information table; the pathological specimen information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the doctor ID, a field 4 which is the examination date, a field 5 which is the interface table main key ID and a field 6 which is the name of the pathological sample;

the nursing information block comprises a nursing information table; the nursing information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the measurement time, a field 5 which is the project name and a field 6 which is the interface table main key ID;

the expense recording block comprises an expense recording information table; the expense record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID and a field 4 which is the interface table main key ID;

the radiotherapy recording block comprises a radiotherapy recording information table; the radiotherapy record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the radiotherapy starting time and a field 5 which is the interface table main key ID;

the chemotherapy recording block comprises a chemotherapy recording information table; the chemotherapy record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID and a field 4 which is the interface table main key ID;

the cancer pain treatment area comprises a cancer pain treatment information table; the cancer pain treatment information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is a patient ID, a field 3 which is a clinic ID and a field 4 which is a main key ID of an interface table;

the instrument use record block comprises an instrument use record information table; the instrument use record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the start use date, a field 5 which is the end use date, a field 6 which is the instrument name, a field 7 which is the interface table main key ID and a field 8 which is the doctor ID;

the medical record information block comprises a medical record home page information table, a medical record home page diagnosis information table, a medical record home page operation information table and a medical record home page attached page information table;

the medical record home page information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID and a field 4 which is the interface table main key ID;

the medical record first page diagnosis information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the treatment ID, a field 4 which is the diagnosis type, a field 5 which is the diagnosis description and a field 6 which is the interface table main key ID;

the medical record homepage operation information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is a patient ID, a field 3 which is a doctor ID, a field 4 which is an operation date, a field 5 which is an operation name and a field 6 which is a main key ID of an interface table;

the medical record homepage supplementary page information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the doctor ID and a field 4 which is the interface table main key ID.

As an implementation manner, the registration record information table further includes byte 4 as the number of times of treatment, byte 5 as the appointment ID, byte 6 as the department of registration, byte 7 as the physician of registration, byte 8 as the registration fee, byte 9 as the patient's name, byte 10 as the fee type, byte 11 as the invoice number, byte 12 as the outpatient service identification, byte 13 as the logout identification, byte 14 as the registrant, byte 15 as the registration time, byte 16 as the registration state, and byte 17 as the registration record generation time;

the clinic information table also comprises byte 7 as the clinic end time, byte 8 as the doctor ID, byte 9 as the medical institution ID, byte 10 as the department ID, byte 11 as the admission condition, byte 12 as the ward, byte 13 as the bed, byte 14 as the observation, byte 15 as the rescue mark, byte 16 as the review mark, byte 17 as the re-admission mark, byte 18 as the discharge department, byte 19 as the leaving mode, byte 20 as the clinic age, byte 21 as the chemotherapy, byte 22 as the radiotherapy and byte 23 as the medical insurance and payment type;

the diagnosis information table further comprises byte 10 as diagnosis end time, byte 11 as stop reason, byte 12 as doctor ID, byte 13 as diagnosis code, byte 14 as department ID, byte 15 as diagnosis source, byte 16 as diagnosis serial number, byte 17 as transfer and byte 18 as recurrence;

the medication information table further comprises a field 10 for stopping reason, a field 11 for medicine continuing times, a field 12 for total amount, a field 13 for days, a field 14 for medicine specification, a field 15 for medication route, a field 16 for single dose, a field 17 for single dose unit, a field 18 for batch, a field 19 for doctor ID, a field 20 for original name of medication route, a field 21 for department ID, a field 22 for medication route coding, a field 23 for package specification, a field 24 for medicine property, a field 25 for RCPT number, a field 26 for dosage form, a field 27 for medical order state and a field 28 for medical order state change time;

the non-medication prescription medical advice information table further comprises a field 7 which is ending time, a field 8 which is a long-term temporary medical advice mark, a field 9 which is medical advice item coding, a field 10 which is medical advice type, a field 11 which is medical advice description, a field 12 which is doctor ID, a field 13 which is department ID, a field 14 which is data warehousing time, a field 15 which is executive name, a field 16 which is executive ID, a field 17 which is medical advice state and a field 18 which is medical advice state change time;

the laboratory test information table further comprises a field 9 which is detection time, a field 10 which is test type, a field 11 which is test value exception symbol, a field 12 which is numerical result, a field 13 which is non-numerical result, a field 14 which is test result unit, a field 15 which is reference value lower limit, a field 16 which is reference value upper limit, a field 17 which is doctor ID, a field 18 which is test large class name, a field 19 which is test large class code, a field 20 which is specimen code, a field 21 which is specimen name, a field 22 which is specimen receiving date, a field 23 which is report date, a field 24 which is department ID and a field 25 which are data updating time;

the microorganism detection information table also comprises a field 9 which is a printing serial number, a field 10 which is a detection package name, a field 11 which is a detection project name, a field 12 which is a drug susceptibility test drug, a field 13 which is a drug susceptibility test result value and a field 14 which is a detection time;

the surgical operation information table further includes a field 9 of surgical grade, a field 10 of surgical site, a field 11 of number of surgeries, a field 12 of doctor ID, a field 13 of surgical code, a field 14 of surgical type, a field 15 of primary doctor code, a field 16 of primary doctor name, a field 17 of I help, a field 18 of II help, a field 19 of anesthesia mode, a field 20 of surgical expiration time, a field 21 of relevant clinical diagnosis, a field 22 of preoperative diagnosis, a field 23 of intraoperative diagnosis, a field 24 of postoperative diagnosis, a field 25 of surgical incision grade, a field 26 of incision healing grade, a field 27 of surgical procedure description, a field 28 of intraoperative diagnosis, a field 29 of intraoperative accident, a field 30 of skin disinfection condition, a field 31 of image number, a a field 32 is a surgical history mark, a field 33 is a bleeding volume, a field 34 is a transfusion volume, a field 35 is an intraoperative blood transfusion volume, a field 36 is an autologous blood transfusion volume, a field 37 is a preoperative resume, a field 38 is a preoperative drug, a field 39 is an intraoperative drug, a field 40 is a surgical room number, a field 41 is a surgical room name, a field 42 is a surgical position, a field 43 is a pre-anesthesia drug, a field 44 is an anesthetic drug, a field 45 is an anesthesia complication, a field 46 is an anesthesiologist, a field 47 is a postoperative complication, a field 48 is postoperative analgesia, a field 49 is a postoperative patient destination, a field 50 is a postoperative return visit, a field 51 is an implant, a field 52 is a same-platform guide, a field 53 is an endoscopic surgery history, a field 54 is an anesthesia start time and a field 55 is an anesthesia end time;

the pathological specimen information table further comprises a field 7 which is a sample type, a field 8 which is a collected sample number, a field 9 which is an anatomical part, a field 10 which is a sample weight, a field 11 which is a positive, a field 12 which is a doctor ID, a field 13 which is a department ID and a field 14 which is a pathological diagnosis code;

the nursing information table also comprises a field 7 for project coding and a field 8 for medical staff ID;

the fee record information table also comprises a field 5 for total fee, a field 6 for total payment, a field 7 for medical insurance payment, a field 8 for patient payment, a field 9 for patient payment of apportioned payment, a field 10 for patient payment of percentage of common insurance fee, a field 11 for patient payment of exemption amount, a field 12 for main payer payment, a field 13 for drug fee, a field 14 for dispensing fee and a field 15 for contract negotiation amount;

the radiotherapy record information table further comprises a field 6 which is radiotherapy ending time, a field 7 which is radiotherapy duration, a treatment purpose, a field 8 which is a radioactive source, a field 9 which is radiotherapy mode, a field 10 which is radiotherapy technology, a field 11 which is radiotherapy part and dose, a field 12 which is radiotherapy times, a field 13 which is radiotherapy word dose, a field 14 which is radiotherapy total dose, a field 15 which is radiotherapy interruption days, a field 16 which is interruption reason, a field 17 which is curative effect evaluation code and a field 18 which is curative effect evaluation;

the chemotherapy record information table further comprises a field 5 for a chemotherapy scheme, a field 6 for a chemotherapy scheme code, a field 7 for a chemotherapy type, a field 8 for a chemotherapy type code, a field 9 for a chemotherapy cycle scheme, a field 10 for a medication record corresponding to a chemotherapy drug, a field 11 for a chemotherapy cycle count, a field 12 for a total number of chemotherapy cycles, a field 13 for a chemotherapy purpose, a field 14 for an interruption reason, a field 15 for a doctor ID, a field 16 for an order execution nurse ID, a field 17 for an order execution nurse name and a field 18 for an order execution result;

the cancer pain treatment information table further comprises a field 5 for current diagnosis, a field 6 for pain cause, a field 7 for hospitalization for pain condition, a field 8 for a physician in charge, a field 9 for a medication record corresponding to a basic drug, a field 10 for a medication record corresponding to an outbreak pain, and a field 11 for an outbreak pain score;

the case homepage information table further comprises a field 5 of hospital admission times, a field 6 of clinic attendance types, a field 7 of institution names, a field 8 of medical insurance numbers, a field 9 of health card numbers, a field 10 of medical payment methods, a field 11 of hospital admission dates, a field 12 of hospital admission departments, a field 13 of hospital admission departments, a field 14 of special department departments, a field 15 of hospital discharge dates, a field 16 of hospital discharge departments, a field 17 of hospital discharge departments, a field 18 of actual hospital admission days, a field 19 of confirmed hospital admission dates, a field 20 of total hospital infection times, a field 21 of injuries, a field 22 of external factor names of poisoning, a field 23 of allergens, a field 24 of allergic drugs, a field 25 of clinic and discharge diagnostic coincidence, a field 26 of hospital and discharge diagnostic coincidence, a field 27 of clinic and pathological diagnosis coincidence, a field 28 of radiation and pathological diagnosis coincidence, a field 29 of rescue times, a field 30 of nurse subjects, a field 31 of doctors, a field 32 of doctors, a doctor and discharge diagnostic coincidence, a field 33 of intensive care days, a field 37 of intensive care days, a field 35 of intensive care days, a field 35, a field of intensive care time control days of intensive care, a field 38, a primary care time of intensive care time of nursing care, a field 38, a field and a primary care time of nursing care;

the first page diagnostic information table of the medical record also comprises a field 7 for diagnostic codes, a field 8 for admission and a field 9 for discharge;

the medical record homepage operation information table also comprises a field 7 which is an operation grade, a field 8 which is an operation position, a field 9 which is an anesthesia mode, a field 10 which is an anesthesia grade and a field 11 which is a healing grade;

the information table of the first page of the medical record also comprises a field 5 for judging whether a new tumor is found, a field 6 for judging the grade of the tumor stage, a field 7 for judging the type of the tumor stage, a field 8 for judging the TNM comprehensive stage, a field 9 for judging the type of the operation, a field 10 for judging the complication, a field 11 for judging the complication and a field 12 for using antibacterial drugs.

As an implementable embodiment, the information block further comprises a patient data information block; the patient data information block comprises a patient information table; the patient information table comprises a patient ID of a field 1, a main key ID of an interface table of a field 2, a sex of a field 3, a year, month and day of birth of a field 4, a ethnicity of a field 5, a race of a field 6, a medical institution ID of a field 7, a name of a field 8, a home address of a field 9, a contact of a field 10, a contact phone of a field 11, a relation of a field 12 with a contact, a native place of a field 13, a certificate number of a field 14, a social security card number of a field 15, a telephone loss of a field 16, an occupation of a field 17, a marital status of a field 18, a work unit of a field 19, a cultural degree of a field 20, a height of a field 21, a weight of a field 22, a blood type of a field 23, a RH blood type of a field 24, a nationality of a field 25 and an age of a first diagnosis of a field 26.

As an implementation, the information block further comprises a hospital data information block; the hospital data information block comprises a medical institution information table, a department ward information table, a medical staff information table, a medication dictionary information table, a diagnosis and treatment project dictionary information table, a disease dictionary information table, an operation dictionary information table and a medical equipment dictionary information table;

the medical institution information table comprises a byte 1 as a hospital number, a byte 2 as a hospital name, a byte 3 as a hospital address, a byte 4 as a hospital zip code and a byte 5 as a hospital building area;

the department ward information table comprises a department ID (identity) in byte 1, a department name in byte 2, a department number in byte 3, a department name in byte 4, department remark information in byte 5, a hospital number in byte 6 and a category in byte 7;

the medical staff information table comprises a doctor ID in byte 1, a doctor name in byte 2, a doctor gender in byte 3, a department name in byte 4, a department number in byte 5, a nurse in byte 6 and a technician and job title in byte 7;

the medication dictionary information table includes byte 1 as a drug code, byte 2 as a drug name, byte 3 as content information reflecting a drug, byte 4 as a dosage form, byte 5 as a toxicology classification, byte 6 as a drug type, byte 7 as a manufacturer, byte 8 as a price, and byte 9 as a supplier;

the diagnosis and treatment item dictionary information table comprises a byte 1 as an item code, a byte 2 as an item name, a byte 3 as an item serial number, a byte 4 as an item large class, a byte 5 as an item category, a byte 6 as a specification, a byte 7 as a unit, a byte 8 as an execution department, a byte 9 as a price, a byte 10 as a manufacturer and a byte 11 as a supplier;

the disease dictionary information table includes byte 1 as a diagnostic code, byte 2 as a diagnostic name, byte 3 as a standardized flag, and byte 4 as a diagnostic category;

the operation dictionary information table comprises a byte 1 as an operation code, a byte 2 as an operation name, a byte 3 as a standardization mark and a byte 4 as an operation grade;

the medical device dictionary information table includes that byte 1 is a device unique number, byte 2 is a device code, byte 3 is a device name, byte 4 is a device model, byte 5 is a device tag number, byte 6 is a device version, byte 7 is a manufacturer, and byte 8 is a supplier.

Referring to fig. 2, the clinical data storage system for a clinical medical universal data structure model includes a clinical relevant data extraction module 100, a data storage module 200, an information table setting module 300 and an information association module 400;

the clinical relevant data extraction module 100 is configured to extract multi-modal clinical relevant data;

the data storage module 200 is configured to store the multi-modal clinical relevant data in different information blocks of a clinical medical general data structure model in a classified manner, where the information blocks include clinical data information blocks;

the information table setting module 300 is configured to set one or more information tables in each clinical data information block;

the information association module 400 is configured to set a patient ID and a visit ID in at least one information table, regard the patient ID as an identifier of the patient in the clinical medical general data structure model, associate the information table related to the patient ID in the clinical medical general data structure model through the patient ID, and integrate all data of the patient in all clinical medical general data structure models; and taking the visit ID as a single visit identifier of the patient in the clinical medical universal data structure model, associating all information tables related to the visit ID in the clinical medical universal data structure model through the visit ID, integrating to obtain all data of the patient in a single visit, setting an interface table main key ID corresponding to the information table in the information table, and associating the original data of the information table through the interface table main key ID.

As an implementation, in the clinical relevant data extraction module, the multi-modal clinical relevant data is extracted by a natural language processing technology.

the imaging omics information table further comprises a group byte 6 as the name of the omics characteristics and a byte 7 as the result of the omics characteristics.

the registration recording block comprises a registration recording information table; the registration record information table comprises a registration ID (identification) field 1, a patient ID field 2, a main key ID field 3 and a clinic ID field 4;

the diagnosis information block comprises a diagnosis information table, wherein the diagnosis information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the diagnosis ID, a field 4 which is the diagnosis start time, a field 5 which is the original name of diagnosis, a field 6 which is the main key ID of an interface table, a field 7 which is the diagnosis code, a field 8 which is the diagnosis standardized name and a field 9 which is the diagnosis type;

the medication information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the medicine name, a field 5 which is the start time, a field 6 which is the end time, a field 7 which is the original name of the medicine, a field 8 which is the main key ID of the interface table and a field 9 which is the medicine type;

the non-medication prescription medical order information table comprises a field 1 as a unique identification ID of the table, a field 2 as a patient ID, a field 3 as a treatment ID, a field 4 as a main key ID of an interface table, a field 5 as a medical order item name and a field 6 as start time;

the laboratory test information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the name of a small item to be tested, a field 5 which is the test time, a field 6 which is the original name of the small item to be tested, a field 7 which is the ID of a main key of an interface table and a field 8 which is the original value of a test result;

the microbial testing information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the item number, a field 5 which is the instrument number, a field 6 which is the colony number and a field 7 which is the main key ID of the interface table;

the operation information block comprises an operation information table; the operation information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the operation name, a field 5 which is the operation standardized name, a field 6 which is the operation starting time, a field 7 which is the operation name of the operation interface table and a field 8 which is the main key ID of the interface table;

the nursing information block comprises a nursing information table; the nursing information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the measurement time, a field 5 which is the project name and a field 6 which is the interface table main key ID;

the cancer pain treatment zone comprises a cancer pain treatment information table; the cancer pain treatment information table comprises a field 1 as a unique identification ID of the table, a field 2 as a patient ID, a field 3 as a clinic ID and a field 4 as a main key ID of an interface table;

the instrument use record block comprises an instrument use record information table; the instrument use record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the clinic ID, a field 4 which is the start use date, a field 5 which is the end use date, a field 6 which is the instrument name, a field 7 which is the interface table main key ID and a field 8 which is the doctor ID;

the diagnosis information table further comprises byte 10 as diagnosis end time, byte 11 as a stop reason, byte 12 as a doctor ID, byte 13 as a diagnosis code, byte 14 as a department ID, byte 15 as a diagnosis source, byte 16 as a diagnosis serial number, byte 17 as whether to transfer and byte 18 as whether to relapse;

the medication information table further comprises a field 10 for a reason of stopping, a field 11 for the number of times of taking medicine, a field 12 for the total amount, a field 13 for the number of days, a field 14 for a medication instruction, a field 15 for a medication route, a field 16 for a single dose, a field 17 for a single dose unit, a field 18 for a batch, a field 19 for a doctor ID, a field 20 for an original name of the medication route, a field 21 for a department ID, a field 22 for a medication route code, a field 23 for a package specification, a field 24 for a medication property, a field 25 for an RCPT number, a field 26 for a dosage form, a field 27 for a medical order state and a field 28 for a change time of the medical order state;

the surgical operation information table further includes a field 9 of surgical grade, a field 10 of surgical site, a field 11 of number of surgeries, a field 12 of doctor ID, a field 13 of surgical code, a field 14 of surgical type, a field 15 of primary doctor code, a field 16 of primary doctor name, a field 17 of I help, a field 18 of II help, a field 19 of anesthesia mode, a field 20 of surgical expiration time, a field 21 of relevant clinical diagnosis, a field 22 of preoperative diagnosis, a field 23 of intraoperative diagnosis, a field 24 of postoperative diagnosis, a field 25 of surgical incision grade, a field 26 of incision healing grade, a field 27 of surgical procedure description, a field 28 of intraoperative diagnosis, a field 29 of intraoperative accident, a field 30 of skin disinfection condition, a field 31 of image number, a the field 32 is a mark of operation history, the field 33 is bleeding volume, the field 34 is infusion volume, the field 35 is intraoperative blood transfusion volume, the field 36 is autologous blood transfusion volume, the field 37 is a preoperative resume, the field 38 is preoperative medication, the field 39 is intraoperative medication, the field 40 is a number of an operation room, the field 41 is a name of the operation room, the field 42 is an operation position, the field 43 is medication before anesthesia, the field 44 is medication during anesthesia, the field 45 is anesthesia complication, the field 46 is an anesthesiologist, the field 47 is complication after the operation, the field 48 is postoperative analgesia, the field 49 is a destination of a postoperative patient, the field 50 is postoperative return visit, the field 51 is an implant, the field 52 is a co-patient guidance, the field 53 is an endoscopic surgery history, the field 54 is anesthesia start time, and the field 55 is anesthesia end time;

the cancer pain treatment information table also comprises a field 5 for current diagnosis, a field 6 for pain causing reasons, a field 7 for hospitalization for pain conditions, a field 8 for a physician in charge, a field 9 for a medication record corresponding to a basic drug, a field 10 for a medication record corresponding to breakthrough pain, and a field 11 for a score of the breakthrough pain;

the medical record homepage information table also comprises a field 5 of hospitalization times, a field 6 of clinic types, a field 7 of institution names, a field 8 of medical insurance numbers, a field 9 of health card numbers, a field 10 of medical payment modes, a field 11 of admission dates, a field 12 of admission departments, a field 13 of admission departments, a field 14 of special departments, a data center and a data center, wherein the field 5 of hospital visits, the field 6 of hospital insurance numbers, the field 9 of hospital admission dates, the field 10 of hospital payment modes, the field 11 of hospital admission dates, the field 12 of admission departments, the field 13 of hospital admission departments, the field 14 of special departments, the data center and the data center are all arranged in a hospital. The field 15 is the date of discharge, the field 16 is the department of discharge, the field 17 is the department of discharge, the field 18 is the actual number of days of stay, the field 19 is the date of the diagnosis after the admission, the field 20 is the total number of nosocomial infections, the field 21 is the lesions, the field 22 is the name of the external factor of the intoxication, the field 23 is the allergen, the field 24 is the allergen, the a field 25 is the outpatient and discharge diagnosis coincidence, a field 26 is the admission and discharge diagnosis coincidence, a field 27 is the clinical and pathological diagnosis coincidence, a field 28 is the radiation and pathological diagnosis coincidence, a field 29 is the rescue times, a field 30 is the chief deputy, a field 31 is the treating physician, a field 32 is the inpatient, a field 33 is the responsible nurse, a field 34 is the quality control physician, a field 35 is the trick care days, a field 36 is the primary care days, a field 37 is the secondary care days, a field 38 is the tertiary care days, a field 39 is the intensive care unit name, a field 40 is the intensive care unit entry time, and a field 41 is the intensive care unit exit time;

the medical record front page diagnosis information table also comprises a field 7 for diagnosis codes, a field 8 for admission conditions and a field 9 for discharge conditions;

the information table of the first page of the medical record also comprises a field 5 for judging whether a new tumor is found, a field 6 for judging the grade of the tumor stage, a field 7 for judging the type of the tumor stage, a field 8 for judging the TNM comprehensive stage, a field 9 for judging the type of the operation, a field 10 for marking complications, a field 11 for marking complications and a field 12 for using antibacterial drugs.

As an implementable embodiment, the information block further comprises a patient data information block; the patient data information block comprises a patient information table; the patient information table includes a patient ID field 1 and a primary key ID field 2 for an interface table, a gender field 3, a year, month, day of birth field 4, a ethnicity field 5, a ethnicity field 6, a medical institution ID field 7, a name field 8, a home address field 9, a contact field 10, a contact phone field 11, a contact relationship field 12, a country field 13, a certificate number field 14, a social security card number field 15, a telephone call loss field 16, a professional field 17, a marital status field 18, a work unit field 19, a culture degree field 20, a height field 21, a weight field 22, a blood type field 23, an RH blood type field 24, a nationality field 25, and an age field 26.

the medical staff information table comprises bytes 1, 2, 3, 4, 5, 6 and 7, wherein the bytes are doctor ID, doctor name, department number and nurse respectively, the doctor ID is in byte 1, the doctor name is in byte 2, the doctor gender is in byte 3, the department name is in byte 4, the department number is in byte 5, and the technician and job title are in byte 6;

The invention also provides a clinical medical data query method, which is based on the clinical data storage system of the clinical medical general data structure model and queries all data of the patient in the clinical data storage system of the clinical medical general data structure model through the patient ID.

Referring to fig. 3, the querying all data of the patient in the clinical data storage system of the clinical medical universal data structure model by the patient ID includes:

inputting the patient ID;

and if a plurality of information tables exist, removing the same information in the information tables, reserving different information, and integrating all data of the patient in the clinical data storage system of the clinical medical general data structure model according to the different information.

All data of the patient at a single visit in the clinical data storage system of the clinical medical universal data structure model can be queried through the visit ID.

As an implementation manner, the querying, by the visit ID, all data of the patient at a single visit in the clinical data storage system of the clinical medical universal data structure model includes:

inputting the visit ID;

finding out one or more information tables with the same treatment ID from all the information tables;

Referring to fig. 4, the clinical medical data query system is a clinical data storage system based on the clinical medical universal data structure model, and further includes a patient all data query module 10;

the patient all-data query module 10 is configured to query all data of the patient in the clinical data storage system of the clinical medical universal data structure model by the patient ID.

Specifically, the patient-owned data query module 10 includes an input unit 11, an information table lookup unit 12, and a data integration unit 13;

the input unit 11 is used for inputting the patient ID;

the information table look-up unit 12 is configured to find one or more information tables with the same patient ID from all the information tables;

the data integration unit 13 is configured to, if there are multiple information tables, remove the same information in the information tables, retain different information, and integrate all data of the patient in the clinical data storage system of the clinical medical general data structure model according to the different information.

As an implementation mode, the system further comprises a patient single-visit data query module 20;

the patient single-visit data query module 20 is configured to query all data of the patient at a single visit in the clinical data storage system of the clinical medical general data structure model by the visit ID.

As an implementation manner, the patient single-visit data query module 20 includes an input unit 21, an information table lookup unit 22 and a data integration unit 23;

the input unit 21 is configured to input the visit ID;

the information table searching unit 22 is used for searching one or more information tables with the same treatment ID from all the information tables;

the data integration unit 23 is configured to, if there are multiple information tables, remove the same information in the information tables, retain different information, and integrate all data of the patient in a single visit in the clinical data storage system of the clinical medical general data structure model according to the different information.

Finally, it is noted that the above-mentioned embodiments illustrate rather than limit the invention, and that, while the invention has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A clinical data storage method of a clinical medical universal data structure model is characterized by comprising the following steps:

extracting multi-modal clinically relevant data;

setting one or more information tables in each clinical data information block;

2. The clinical data storage method of the clinical medical general data structure model according to claim 1, wherein the extracting the multi-modal clinical relevant data comprises: clinically relevant data for multiple modalities is extracted by natural language processing techniques.

3. The method for clinical data storage according to claim 1, wherein the multi-modal clinical-related data includes HIS, LIS, EMR, image, pathology, and natural language processing information.

4. The method for clinical data storage according to the clinical medical universal data structure model of claim 3, wherein the multi-modal clinical relevant data is derived from oracle, mysql, sql server and/or hbase database.

5. The clinical data storage method of the clinical medical universal data structure model as claimed in claim 1, wherein the clinical data information block comprises a text record block;

the natural language processing information table comprises a field 1 which is a unique identification ID of the table, a field 2 which is an external key of the natural language processing information table, a field 3 which is a processing date, a field 4 which is a paragraph name of data from an original text, a field 5 which is a text window of data, a field 6 which is a character offset of the data in the whole text, a field 7 which is a main key ID of an interface table, a field 8 which is a standard concept name after the original text is subjected to standardization processing, a field 9 which is a name and a version of an NLP system for extracting the standard concept name, a field 10 which is a relational attribute value of the field 7, and a field 11 which is a relational attribute type of the field 10 and the field 7.

6. The clinical data storage method of the clinical medical universal data structure model according to claim 5, wherein the clinical data information block comprises a surgical examination information block;

the image sequence information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the associated examination ID, a field 3 which is the patient ID, a field 4 which is the diagnosis ID and a field 5 which is the main key ID of an interface table;

the imaging omics information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the primary key ID associated with the influence sequence example table and a field 5 which is the primary key ID of the interface table.

7. The clinical data storage method of the clinical medical universal data structure model according to claim 6,

the image sequence information table further comprises a DICOM generation date of byte 6, a serial number of byte 7, a layer thickness of byte 8, a position of byte 9, a window level of byte 10, a window width of byte 11, a line resolution of byte 12, a column resolution of byte 13, a position of byte 14, a slope of byte 15 and a sequence set file directory of byte 16;

8. The clinical data storage method of the clinical medical universal data structure model according to claim 1, wherein the clinical data information block comprises at least one of a registration record block, a medical visit information block, a diagnosis information block, a prescription order information block, a test information block, a surgical procedure information block, an examination information block, a pathology specimen information block, a care information block, a text record block, a cost record block, a radiotherapy record block, a chemotherapy record block, a cancer pain treatment block, an instrument usage record block, and a medical record information block;

the diagnosis information block comprises a diagnosis information table, wherein the diagnosis information table comprises a field 1 which is a table unique identification ID, a field 2 which is a patient ID, a field 3 which is a diagnosis ID, a field 4 which is a diagnosis start time, a field 5 which is a diagnosis original name, a field 6 which is an interface table main key ID, a field 7 which is a diagnosis code, a field 8 which is a diagnosis standardized name and a field 9 which is a diagnosis type;

the medication information table comprises a field 1 which is a table unique identification ID, a field 2 which is a patient ID, a field 3 which is a clinic ID, a field 4 which is a medicine name, a field 5 which is a start time, a field 6 which is an end time, a field 7 which is a medicine original name, a field 8 which is an interface table main key ID and a field 9 which is a medicine type;

the non-medication prescription medical advice information table comprises a field 1 which is a table unique identification ID, a field 2 which is a patient ID, a field 3 which is a treatment ID, a field 4 which is a main key ID of an interface table, a field 5 which is a medical advice item name and a field 6 which is a starting time;

the chemotherapy recording block comprises a chemotherapy recording information table; the chemotherapy record information table comprises a field 1 as the unique identification ID of the table, a field 2 as the patient ID, a field 3 as the visit ID and a field 4 as the interface table main key ID;

9. The clinical data storage method for the clinical medical universal data structure model according to claim 8,

the registration record information table further comprises byte 4 as diagnosis and treatment times, byte 5 as an appointment ID, byte 6 as a registration department, byte 7 as a registration doctor, byte 8 as a registration fee, byte 9 as a patient name, byte 10 as a fee type, byte 11 as an invoice number, byte 12 as an outpatient service identification, byte 13 as a logout identification, byte 14 as a registrant, byte 15 as registration time, byte 16 as a registration state and byte 17 as registration record generation time;

the microorganism detection information table also comprises a field 9 which is a printing serial number, a field 10 which is a detection package name, a field 11 which is a detection project name, a field 12 which is drug sensitivity test medication, a field 13 which is a drug sensitivity test result value and a field 14 which is detection time;

the surgical operation information table further includes a field 9 of surgical grade, a field 10 of surgical site, a field 11 of surgical quantity, a field 12 of doctor ID, a field 13 of surgical code, a field 14 of surgical type, a field 15 of primary doctor code, a field 16 of primary doctor name, a field 17 of auxiliary I, a field 18 of auxiliary II, a field 19 of anesthesia mode, a field 20 of surgical expiration time, a field 21 of relevant clinical diagnosis, a field 22 of preoperative diagnosis, a field 23 of intraoperative diagnosis, a field 24 of postoperative diagnosis, a field 25 of surgical incision grade, a field 26 of incision healing grade, a field 27 of surgical procedure description, a field 28 of intraoperative observation, a field 29 of intraoperative accident, a field 30 of skin disinfection condition, a field 31 of image number, a field the field 32 is a mark of operation history, the field 33 is bleeding volume, the field 34 is infusion volume, the field 35 is intraoperative blood transfusion volume, the field 36 is autologous blood transfusion volume, the field 37 is a preoperative resume, the field 38 is preoperative medication, the field 39 is intraoperative medication, the field 40 is a number of an operation room, the field 41 is a name of the operation room, the field 42 is an operation position, the field 43 is medication before anesthesia, the field 44 is medication during anesthesia, the field 45 is anesthesia complication, the field 46 is an anesthesiologist, the field 47 is complication after the operation, the field 48 is postoperative analgesia, the field 49 is a destination of a postoperative patient, the field 50 is postoperative return visit, the field 51 is an implant, the field 52 is a co-patient guidance, the field 53 is an endoscopic surgery history, the field 54 is anesthesia start time, and the field 55 is anesthesia end time;

the pathological specimen information table also comprises a field 7 which is a sample type, a field 8 which is a collected sample number, a field 9 which is an anatomical part, a field 10 which is a sample weight, a field 11 which is a positive, a field 12 which is a doctor ID, a field 13 which is a department ID and a field 14 which is a pathological diagnosis code;

the medical record homepage information table further comprises a field 5 of hospitalization times, a field 6 of clinic types, a field 7 of institution names, a field 8 of medical insurance numbers, a field 9 of health card numbers, a field 10 of medical payment methods, a field 11 of admission dates, a field 12 of hospital departments, a field 13 of hospital departments, a field 14 of special departments, a field name of institution names the date of discharge in field 15, department of discharge in field 16, ward of discharge in field 17, actual days of hospitalization in field 18, date of confirmed diagnosis after admission in field 19, total number of nosocomial infections in field 20, lesions in field 21, name of external factors of intoxication in field 22, allergen in field 23, allergen in field 24, and the field 25 is the outpatient service and discharge diagnosis coincidence, the field 26 is the admission and discharge diagnosis coincidence, the field 27 is the clinical and pathological diagnosis coincidence, the field 28 is the radiation and pathological diagnosis coincidence, the field 29 is the rescue times, the field 30 is the chief deputy, the field 31 is the treating physician, the field 32 is the inpatient, the field 33 is the responsible nurse, the field 34 is the quality control physician, the field 35 is the special nursing days, the field 36 is the primary nursing days, the field 37 is the secondary nursing days, the field 38 is the tertiary nursing days, the field 39 is the intensive care department name, the field 40 is the intensive care department entry time, and the field 41 is the intensive care department exit time;

10. A clinical data storage method of the clinical medical universal data structure model according to claim 1, wherein the information block further comprises a patient data information block; the patient data information block comprises a patient information table; the patient information table includes a patient ID field 1 and a primary key ID field 2 for an interface table, a gender field 3, a year, month, day of birth field 4, a ethnicity field 5, a ethnicity field 6, a medical institution ID field 7, a name field 8, a home address field 9, a contact field 10, a contact phone field 11, a contact relationship field 12, a country field 13, a certificate number field 14, a social security card number field 15, a telephone call loss field 16, a professional field 17, a marital status field 18, a work unit field 19, a culture degree field 20, a height field 21, a weight field 22, a blood type field 23, an RH blood type field 24, a nationality field 25, and an age field 26.

11. The clinical data storage method of the clinical medical universal data structure model as claimed in claim 1, wherein the information block further comprises a hospital data information block; the hospital data information block comprises a medical institution information table, a department ward information table, a medical staff information table, a medication dictionary information table, a diagnosis and treatment project dictionary information table, a disease dictionary information table, an operation dictionary information table and a medical equipment dictionary information table;

the medical device dictionary information table comprises that byte 1 is a unique device number, byte 2 is a device code, byte 3 is a device name, byte 4 is a device model, byte 5 is a device tag number, byte 6 is a device version, byte 7 is a manufacturer and byte 8 is a supplier.

12. A clinical data storage system of a clinical medical universal data structure model is characterized by comprising a clinical relevant data extraction module, a data storage module, an information table setting module and an information correlation module;

13. The clinical data storage system of the clinical medical general data structure model as claimed in claim 12, wherein in the clinical relevant data extraction module, the multi-modal clinical relevant data is extracted by a natural language processing technique.

14. The clinical data storage system for the clinical medical universal data structure model as claimed in claim 12, wherein the multi-modal clinical-related data includes HIS, LIS, EMR, image, pathology, genetic and natural language processing information.

15. The clinical data storage system according to claim 12, wherein the multimodal clinically relevant data is derived from oracle, mysql, sql server and/or hbase databases.

16. The clinical data storage system according to claim 12, wherein the clinical data information block comprises a text record block;

the admission record information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the record time and a field 5 which is the interface table main key ID;

17. The clinical data storage system according to claim 16, wherein the clinical data information block comprises a surgical examination information block;

18. The clinical data storage system for the clinical medical universal data structure model according to claim 17,

the image sequence information table further comprises a DICOM generation date of byte 6, a sequence number of byte 7, a layer thickness of byte 8, a position of byte 9, a window level of byte 10, a window width of byte 11, a line resolution of byte 12, a column resolution of byte 13, a position of byte 14, a slope of byte 15 and a sequence set file directory of byte 16;

19. The clinical data storage system of the clinical medical universal data structure model according to claim 12, wherein the clinical data information block comprises at least one of a registration record block, a visit information block, a diagnosis information block, a prescription order information block, a test information block, a surgical procedure information block, an examination information block, a pathological specimen information block, a nursing information block, a text record block, a cost record block, a radiotherapy record block, a chemotherapy record block, a cancer pain treatment block, an instrument usage record block, and a medical record information block;

the pathological specimen information block comprises a pathological specimen information table; the pathological specimen information table comprises a field 1 which is the unique identification ID of the table, a field 2 which is the patient ID, a field 3 which is the visit ID, a field 4 which is the date of the submission, a field 5 which is the main key ID of the interface table and a field 6 which is the name of the pathological sample;

the medical record homepage operation information table comprises a field 1 as a unique identification ID of the table, a field 2 as a patient ID, a field 3 as a doctor ID, a field 4 as an operation date, a field 5 as an operation name and a field 6 as a main key ID of an interface table;

20. The clinical data storage system according to claim 19, wherein the registry information table further comprises byte 4 for number of treatment, byte 5 for appointment ID, byte 6 for registry department, byte 7 for registered physician, byte 8 for registry fee, byte 9 for patient name, byte 10 for fee type, byte 11 for invoice number, byte 12 for outpatient service identification, byte 13 for logout identification, byte 14 for registrant, byte 15 for registry time, byte 16 for registry status and byte 17 for registry generation time;

the clinic information table also comprises byte 7 as the clinic end time, byte 8 as the doctor ID, byte 9 as the medical institution ID, byte 10 as the department ID, byte 11 as the admission situation, byte 12 as the ward, byte 13 as the bed, byte 14 as the observation or not, byte 15 as the rescue identification, byte 16 as the review identification, byte 17 as the re-admission identification, byte 18 as the discharge department, byte 19 as the leaving mode, byte 20 as the clinic age, byte 21 as the chemotherapy or not, byte 22 as the radiotherapy or not and byte 23 as the medical insurance and payment type;

the surgical operation information table further includes a field 9 of surgical grade, a field 10 of surgical site, a field 11 of surgical quantity, a field 12 of doctor ID, a field 13 of surgical code, a field 14 of surgical type, a field 15 of primary doctor code, a field 16 of primary doctor name, a field 17 of auxiliary I, a field 18 of auxiliary II, a field 19 of anesthesia mode, a field 20 of surgical expiration time, a field 21 of relevant clinical diagnosis, a field 22 of preoperative diagnosis, a field 23 of intraoperative diagnosis, a field 24 of postoperative diagnosis, a field 25 of surgical incision grade, a field 26 of incision healing grade, a field 27 of surgical procedure description, a field 28 of intraoperative observation, a field 29 of intraoperative accident, a field 30 of skin disinfection condition, a field 31 of image number, a field a field 32 is a surgical history mark, a field 33 is a bleeding volume, a field 34 is a transfusion volume, a field 35 is an intraoperative blood transfusion volume, a field 36 is an autologous blood transfusion volume, a field 37 is a preoperative resume, a field 38 is a preoperative drug, a field 39 is an intraoperative drug, a field 40 is a surgical room number, a field 41 is a surgical room name, a field 42 is a surgical position, a field 43 is a pre-anesthesia drug, a field 44 is an anesthetic drug, a field 45 is an anesthesia complication, a field 46 is an anesthesiologist, a field 47 is a postoperative complication, a field 48 is postoperative analgesia, a field 49 is a postoperative patient destination, a field 50 is a postoperative return visit, a field 51 is an implant, a field 52 is a same-platform guide, a field 53 is an endoscopic surgery history, a field 54 is an anesthesia start time and a field 55 is an anesthesia end time;

21. A clinical data storage system according to claim 12, wherein said information block further comprises a patient data information block; the patient data information block comprises a patient information table; the patient information table includes a patient ID field 1 and a primary key ID field 2 for an interface table, a gender field 3, a year, month, day of birth field 4, a ethnicity field 5, a ethnicity field 6, a medical institution ID field 7, a name field 8, a home address field 9, a contact field 10, a contact phone field 11, a contact relationship field 12, a country field 13, a certificate number field 14, a social security card number field 15, a telephone call loss field 16, a professional field 17, a marital status field 18, a work unit field 19, a culture degree field 20, a height field 21, a weight field 22, a blood type field 23, an RH blood type field 24, a nationality field 25, and an age field 26.

22. The clinical data storage system of the clinical medical universal data structure model according to claim 12, wherein the information block further comprises a hospital data information block; the hospital data information block comprises a medical institution information table, a department ward information table, a medical staff information table, a medication dictionary information table, a diagnosis and treatment project dictionary information table, a disease dictionary information table, an operation dictionary information table and a medical equipment dictionary information table;

the medical institution information table comprises bytes 1, 2, 3 and 4, hospital numbers, hospital names and hospital building areas, wherein the bytes are the hospital numbers, the bytes are the hospital names, the bytes are the hospital addresses, and the bytes are the hospital zip codes and the bytes are the hospital building areas;

23. A clinical medical data query method, wherein based on the clinical data storage system of the clinical medical universal data structure model according to any one of claims 12 to 22, all data of the patient in the clinical data storage system of the clinical medical universal data structure model is queried through the patient ID.

24. The method for querying clinical medical data according to claim 23, wherein the querying all data of the patient in the clinical data storage system of the clinical medical universal data structure model by the patient ID comprises:

inputting the patient ID;

25. The method of claim 23, wherein all data of a patient at a single visit in the clinical data storage system of the clinical medical universal data structure model are queried by the visit ID.

26. The method as claimed in claim 25, wherein said querying all data of a patient at a single visit in the clinical data storage system of the clinical medical universal data structure model by the visit ID comprises:

inputting the visit ID;

27. A clinical medical data query system, which is a clinical data storage system based on the clinical medical universal data structure model according to any one of claims 12-22, further comprising a patient-specific data query module;

28. The clinical medical data query system according to claim 27, wherein the patient-all data query module includes an input unit, an information table lookup unit, and a data integration unit;

the input unit is used for inputting the patient ID;

the information table searching unit is used for finding one or more information tables with the same patient ID from all the information tables;

29. The clinical medical data query system of claim 27, further comprising a patient single visit data query module;

30. The clinical medical data query system of claim 29, wherein the patient single visit data query module comprises an input unit, an information table lookup unit and a data integration unit;

the input unit is used for inputting the clinic ID;

the information table searching unit is used for searching one or more information tables with the same clinic ID from all the information tables;