CN110838347A - Rare disease information management system based on B/S framework - Google Patents
Rare disease information management system based on B/S framework Download PDFInfo
- Publication number
- CN110838347A CN110838347A CN201911217905.3A CN201911217905A CN110838347A CN 110838347 A CN110838347 A CN 110838347A CN 201911217905 A CN201911217905 A CN 201911217905A CN 110838347 A CN110838347 A CN 110838347A
- Authority
- CN
- China
- Prior art keywords
- rare disease
- rare
- unit
- management component
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9538—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/986—Document structures and storage, e.g. HTML extensions
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Health & Medical Sciences (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention discloses a rare disease information management system based on a B/S (browser/Server) framework, which comprises a Web application server, a client and a database server, wherein the client and the database server are in communication connection with the Web application server. And the client performs data interaction with the Web application server through the Web browser. The Web application server includes: a user identity authentication and authority management component; an audit management component; a metadata management component; the form template management component is in communication connection with the metadata management component; a rare disease knowledge base management component; a rare case data sharing component; and the front-end HTML information publishing component is in communication connection with the rare disease knowledge base management component and the rare disease case data sharing component. The database server comprises a rare disease knowledge database server, a rare disease case database server and a metadata database server. The method is convenient for the public to quickly know the latest disease knowledge, and can assist researchers to develop effective rare disease research, so that the diagnosis efficiency of rare diseases is improved.
Description
Technical Field
The invention relates to the technical field of medical information systems, in particular to a rare disease information management system based on a B/S framework.
Background
The rare diseases are called 'rare diseases' for short, also called 'orphan diseases', and the name suggests that the disease rate is very low and the diseases are rare. Most rare diseases are chronic and serious diseases that are often life threatening. Approximately 80% of rare diseases are caused by genetic defects, and thus rare diseases are generally referred to as "rare genetic diseases". According to the report of the World Health Organization (WHO), more than 5000 recognized rare diseases exist at present, and account for about 10% of the human disease types; about 50 percent of rare diseases can be attacked at birth or in childhood, the disease condition is usually and rapidly progressed, the death rate is high, most of the diseases have no effective treatment method, and great pain is caused to patients.
The rare diseases are relative, dynamic and variable concepts, the definition and the division of the rare diseases do not have a unified standard in different countries and regions of the world, and different definitions of the rare diseases in each country are related to the population, the economic development level, the incentive policy of research and development of rare medicines and the coverage range of diagnosis and treatment costs of the rare diseases. China medical society of medicine, genetics, in 5 and 17 months 2010, held up a conference of related experts in Shanghai, agreed on Chinese rare disease definitions: considering that the population base of China is large, referring to the incidence rate of the rare diseases of regions such as hong Kong and Taiwan and surrounding countries such as Japan, the disease rate of the rare diseases is defined as less than one fiftieth of ten-thousandth; a genetic disease with a prevalence of less than one in ten thousand in newborns can be defined as a rare genetic disease.
Due to the specificity of rare diseases, the related knowledge of the diseases is far from enough popular to the public, and the public often talks about color changes and lacks basic cognition on the rare diseases. For researchers, a large sample of case data must be based on when conducting rare disease studies. However, most research institutions currently create a system for research and management of a certain disease. Most of these systems employ the system architecture of C/S. Only case data acquisition and disease research in a single small range can be realized, effective information cannot be obtained from mass data, and related operations such as coordination work and case sharing among different medical institutions cannot be realized. Because research schemes and required data of different rare diseases are different, researchers need to spend a lot of time and energy to make corresponding research forms to collect corresponding data when researching different rare diseases, and great inconvenience is brought to the researchers. In addition, data among various research institutions form data islands, and the scattering of the same rare disease research data in different medical institutions cannot form a scale sample, which is the biggest problem in rare disease research at present. Furthermore, the research results that can be published externally cannot be published in time, and accurate statistics cannot be carried out on each rare disease case. Furthermore, the rare diseases are mostly genetic diseases, so the causes, development predictions and the like of the rare diseases need to be analyzed from a deeper genetic aspect, which is based on the data of medical websites and databases which are authoritative and have a relatively wide coverage at home and abroad. However, these data are all derived from several scattered and independent website platforms, and when a researcher is doing research or needs to look up relevant medical information, on one hand, the existence of the website is sometimes unclear, and on the other hand, the website cannot be found accurately even if the researcher knows the website, which undoubtedly increases the time consumption.
In view of the above problems in the prior art, there is a need in the art for a rare disease information management system that integrates rare disease case data collection, statistics, analysis, statistical data distribution, research result distribution, disease knowledge popularization, and authoritative medical websites and databases.
Disclosure of Invention
In view of this, an embodiment of the present invention provides a B/S architecture-based rare disease information management system, which can solve the problems that the existing system cannot realize efficient collection, accurate statistics, timely publishing of statistical data, deep research of rare diseases, timely publishing of research results, popularization of disease knowledge, integration of authoritative medical websites and databases, and the like.
In view of the above objects, an aspect of the embodiments of the present invention provides a B/S architecture-based rare disease information management system, including a client, a Web application server communicatively connected to the client via the internet, and a database server communicatively connected to the Web application server via a switch,
the client side performs data interaction with the Web application server through a Web browser,
the Web application server includes:
a user identity authentication and authority management component;
an audit management component;
a metadata management component;
a form template management component in communicative connection with the metadata management component;
a rare disease knowledge base management component;
a rare case data sharing component; and
a front-end HTML information publishing component communicatively coupled to the rare disease knowledge base management component and the rare disease case data sharing component,
the database server comprises a rare disease knowledge database server, a rare disease case database server and a metadata database server.
The B/S architecture-based rare disease information management system as described above, preferably, the clients include a researcher client, a general user client, and an administrator client,
the client of the researcher comprises a user registration information sending unit, a file editing unit, a form template memory, a rare disease data acquisition and transmission unit, and an HTML receiving unit, an HTML analyzing unit and a page display unit which are connected in sequence,
the common user client comprises an HTML receiving unit, an HTML analyzing unit and a page display unit which are connected in sequence,
the administrator client comprises a user registration information sending unit, a data maintenance unit, and an HTML receiving unit, an HTML analyzing unit and a page display unit which are connected in sequence.
In the B/S architecture-based rare disease information management system, preferably, the form template storage stores research form templates made by researchers for respective rare diseases.
In the B/S architecture-based rare disease information management system, preferably, the metadata base server stores metadata and a dictionary, wherein the metadata and the dictionary are required by a researcher when designing a research form template, the metadata includes public metadata and private metadata, and the dictionary includes a public dictionary and a private dictionary.
In the B/S architecture-based rare disease information management system described above, preferably, the rare disease knowledge base management component includes a database access interface connected to a plurality of medical databases.
In the B/S architecture-based rare disease information management system described above, preferably, the plurality of medical databases include at least GeneReviews, CHPO, GeneCards, and MalaCards.
In the B/S architecture-based rare disease information management system, preferably, the rare disease case data sharing component includes a case statistics unit.
In the B/S architecture-based rare disease information management system, preferably, the rare disease knowledge database server stores rare disease related knowledge from a plurality of data sources, and the rare disease case database server stores rare disease case statistical data.
In the B/S architecture-based rare disease information management system, preferably, the Web application server further includes a big data analysis unit connected to the rare disease knowledge base management component.
In the B/S architecture-based rare disease information management system, preferably, the big data analysis unit includes a computing unit and a storage unit, and the computing unit includes a CPU and a GPU.
Advantageous effects
The rare disease information management system based on the B/S framework can assist researchers to design a research form template in an autonomous and visual mode, help the researchers to produce attractive and practical research forms more simply and more quickly, effectively collect relevant case data by using the research forms, then gather the case data collected by the researchers in various hospitals and research institutions through the system, and clean, convert and load the data through a data processing center. Through data processing, an authoritative and timely updated general and special medical data database is formed, a medical data center is constructed, and data retrieval can be directly carried out on the data center. The system can accurately count the summarized case data and release the summarized case data on the portal website in different forms of charts, and the public and all researchers can acquire the information through the portal website without any authority. Meanwhile, a system administrator may perform periodic maintenance on disease knowledge, statistical data, metadata, and the like. In addition, this system with accurate medical platforms such as GeneReviews, CHPO, GeneCards, MalaCards, the database is integrated into, provides more convenient instrument and uses, improves researcher's work efficiency to further promote rare disease clinical diagnosis and treatment ability and promote, also made things convenient for the public to the all-round understanding of rare disease. Moreover, the system provides a channel for acquiring the knowledge related to the rare diseases for the social public, so that the social public can timely know the latest research result of the rare diseases.
Drawings
FIG. 1 is a schematic diagram of a B/S architecture-based rare disease information management system according to an embodiment of the present invention;
FIG. 2 is a schematic block diagram of a researcher client according to one embodiment of the present invention;
FIG. 3 is a schematic block diagram of a generic user client according to one embodiment of the present invention;
FIG. 4 is a schematic block diagram of an administrator client, according to one embodiment of the present invention;
FIG. 5 is a schematic hierarchical architecture diagram of a metadata management component according to one embodiment of the present invention;
FIG. 6 is a schematic hierarchical architecture diagram of a form template management component according to one embodiment of the present invention; and
FIG. 7 is a schematic hierarchical diagram of a rare disease knowledge base management component in accordance with one embodiment of the present invention.
Detailed Description
The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention. Unless otherwise specified, the technical means used in the examples are conventional means well known to those skilled in the art.
In view of the above, the embodiment of the present invention provides an embodiment of a rare disease information management system. The rare disease information management system adopts a B/S (Browser/Server) framework, and the B/S framework adopts a working mode of Browser request and Server response. Fig. 1 is a schematic architecture diagram of the B/S architecture-based rare disease information management system according to the embodiment. As shown in fig. 1, the overall architecture of the B/S architecture based rare disease information management system may include a client 101, a Web application server 102 communicatively connected to the client 101 through the internet, and database servers 104, 105, 106 communicatively connected to the Web application server 102 through a switch 103. The client 101 performs data interaction with the Web application server 102 through a Web browser. The database server software used in this embodiment may be in a version of mysql5.0 or more. The client browser can be various mainstream browsers such as IE, Firefox, Google Chrome and the like. The client shown in fig. 1 may comprise a PC as an example, but it will be appreciated by a person skilled in the art that it may also comprise any mobile terminal. The Web application server 102 may include a user authentication and rights management component 107; an audit management component 108; a metadata management component 109; a form template management component 110 communicatively coupled to the metadata management component 109; a rare disease knowledge base management component 111; a rare case data sharing component 112; and a front-end HTML information publishing component 113 communicatively coupled to the rare disease knowledge base management component 111 and the rare disease case data sharing component 112. In particular, the database servers may include a rare case knowledge database server 104, a rare case database server 105, and a metadata database server 106.
In a preferred embodiment, the clients may include a researcher client, a general user client, and an administrator client.
As shown in fig. 2, the researcher client 20 may include a user registration information sending unit 201, a file editing unit 202, a form template storage 203, a rare disease data acquisition and transmission unit 204, and an HTML receiving unit 205, an HTML parsing unit 206, and a page display unit 207 connected in sequence. The rare disease data acquisition and transmission unit 204 may be connected to existing information collection systems of hospitals and research institutions. The researcher inputs a user name and a password at the researcher client 20 and sends the user name and the password to the Web application server 102 through the user registration information sending unit 201, the user identity authentication and authority management component 107 verifies the login information and distributes the access authority, and after the verification of the login information is passed, the researcher can freely access the system module which is allowed to be accessed according to the authority. The document editing unit 202 may be utilized to edit relevant documents to be submitted when a researcher applies for studying a disease, such as application documents, list of group members for plan writing, list of group members for argumentation experts, startup documents, etc., wherein the application documents may include applicants' resume, application manual, disease introduction, diagnosis criteria, disease cohort study plan, research form, list and unit of makers of research plan and research form, research plan and research form demonstration report, etc., and the startup documents may include ethical approval and informed consent. After the document is edited, the document is uploaded to the Web application server 102, the document is forwarded to a researcher with an auditing authority by the auditing management component 108 for auditing the queue research, the researcher can start the queue research after the auditing is passed, a research form template is designed by using corresponding metadata and a dictionary, and the designed research form template can be stored in the form template storage 203 for subsequent use. Then, the case data collected by the rare disease data collection and transmission unit 204 is recorded into a corresponding study form template to form a complete study form, and the queue study is performed according to the data in the study form. The HTML receiving unit 205 is configured to receive an HTML source file returned by the Web application server 102 in response to a request sent by the client browser, the HTML parsing unit 206 is configured to parse the received HTML source file, implement rendering on a page in the parsing process, and the page display unit 207 is configured to display a finally rendered page.
As shown in fig. 3, the general user client 30 may include an HTML receiving unit 301, an HTML parsing unit 302, and a page display unit 303, which are connected in sequence. The HTML receiving unit 301 is configured to receive an HTML source file returned by the Web application server 102 in response to a request sent by the client browser, the HTML parsing unit 302 is configured to parse the received HTML source file, rendering of a page is achieved in the parsing process, and the page display unit 303 is configured to display a finally rendered page.
As shown in fig. 4, the administrator client 40 may include a user registration information transmitting unit 401, a data maintenance unit 402, and an HTML receiving unit 403, an HTML parsing unit 404, and a page display unit 405 connected in this order. The administrator inputs a user name and a password at the administrator client 40 and sends the user name and the password to the Web application server 102 through the user registration information sending unit 401, the user identity authentication and authority management component 107 verifies the login information and distributes the access authority, and after the verification of the login information is passed, the administrator can freely access the system module which is allowed to be accessed according to the authority. The administrator may utilize the data maintenance unit 402 to perform periodic maintenance on disease knowledge, statistics, metadata, and the like. The HTML receiving unit 403 is configured to receive an HTML source file returned by the Web application server 102 in response to a request sent by the client browser, the HTML parsing unit 404 is configured to parse the received HTML source file, rendering a page is implemented in the parsing process, and the page display unit 405 is configured to display a finally rendered page.
The user authentication and authorization management component 107 manages user registration information and access authorization of various users, and verifies the user registration information of the user when the user logs in an application system of the application server. The user authentication and authorization management component 107 performs authentication through a unified user management mechanism to determine the access content (access authorization) of the user. The personal user password supports end-to-end encryption through the security control, and the password is stored after being encrypted; and limits the number of consecutive login failures.
After receiving the above-mentioned related file which needs to be submitted for researching a certain disease, the audit management component 108 forwards the file to the researcher with audit authority for auditing the queue research, and returns the audit result to the researcher. If the audit is passed, a queue study may be initiated, and if the audit is not passed, the associated file may need to be resubmitted.
FIG. 5 is a schematic hierarchical diagram of a metadata management component according to one embodiment of the present invention. As shown in fig. 5, the overall architecture of the metadata management component 109 is divided into: the system comprises a user layer, a display layer, an application layer, a data layer, a database and a hardware layer. The users of the system are divided into two categories: the system comprises a researcher and a manager, wherein the researcher can manage metadata and dictionaries required by form design of the researcher, and can also use existing public metadata and dictionaries in the system, and the public data needs to be maintained by system managers. The application layer of the system is mainly divided into the following applications: metadata management, comprising: the two types of public metadata and private metadata support the functions of metadata addition, editing, format definition, deletion, backup export, restoration, search and the like; dictionary management, also including: the public dictionary and the private dictionary support functions of adding, editing, deleting, backup exporting, restoring, searching and the like of the dictionary; a system log, comprising: the system comprises a metadata log, a dictionary log and the like, and is mainly used for recording data operation changes of important applications in the system. The metadata may include, for example, the patient's name, gender, age, region, contact, ethnicity, and so on. When making a disease form, a user typically uses data items having an option type, such as metadata with a gender, which has three options: male, female, unknown. The user needs to add a dictionary to this metadata and set a value field to the dictionary. The value range information includes: name, code, input code, operation, etc.
FIG. 6 is a schematic hierarchical diagram of a form template management component according to one embodiment of the invention. As shown in FIG. 6, the overall architecture of the form template management component 110 is divided into: the system comprises a user layer, a display layer, an application layer, a data layer, a database and a hardware layer. The users of the system are researchers and managers, and the users can make research forms of rare diseases through the system. The main application of the system is as follows: form templates, workflow management, system logs, and the like. The application layer of the system is mainly divided into the following applications: form template management, which may maintain form template information, includes but is not limited to: operations such as adding, editing, deleting, searching, designing, previewing, backing up export, restoring and releasing; workflow management, which may maintain workflow information, includes but is not limited to: operations such as adding, editing, deleting, searching, designing, previewing, backing up export, restoring and releasing; a system log, comprising: the system comprises a form template log, a workflow log and the like, and is mainly used for recording data operation changes of important applications in the system.
The rare disease knowledge base management component 111 obtains the rare disease related knowledge (e.g., the research results uploaded by the researcher client, the disease introduction uploaded by the administrator client, the etiology and pathogenesis, the general introduction of the disease types such as clinical manifestations, diagnosis, treatment and prognosis, the related medical terms, and the like, and the resources from a plurality of precision medical websites and databases at home and abroad, etc.), then processes the knowledge data (including but not limited to cleaning, converting, classifying, calculating, etc. of the data), and finally puts the processed data into a database (i.e., stores the processed data on the rare disease knowledge database server 104), for the research results and the accurate medical knowledge, the rare disease knowledge base management component 111 can automatically check whether the rare disease knowledge base can be issued according to preset check rules, the content which can be published externally as disease knowledge is transmitted to the front-end HTML information publishing component 113 to be published on the portal web site in time.
In a preferred embodiment, the rare disease knowledge base management component 111 comprises a database access interface that interfaces with a plurality of medical databases, wherein the plurality of medical databases comprises at least GeneReviews, CHPO, GeneCards, and MalaCards. GeneReviews is an international resource platform, provides clinical knowledge and operation guidance of genetic related diseases for busy clinicians in the form of periodical articles, and relates to aspects of disease diagnosis, management, genetic consultation for patients and the like. The contents of each chapter of GeneReviews are written by experts in the relevant field, and are carefully revised and commented on by peers before being published. CHPO (Chinese Human phenotypeon on biology Consortium) is a Chinese version translation of HPO (Human phenotypeon on biology) intended to provide a standard vocabulary in Human diseases for describing phenotypical abnormalities, each term describing one phenotypical abnormality. HPO founders develop using information obtained from medical literature, oraphanet, DECIPHER, and OMIM databases, and the HPO development group is also continually performing maintenance and completion work on terms. The CHPO is a project participated in by volunteers, aims to establish an open platform in China, combines professional persons in various fields, gradually establishes Chinese clinical phenotype term standards, promotes the application of the HPO in China, and participates in the optimization and updating of the HPO, thereby supporting the clinical and scientific research work of Chinese users. GeneCards are integrated databases that can automatically retrieve data from 125 databases and integrate. Provides detailed information about all annotated or predicted genes in humans, including genomic, transcriptome, proteomic, clinical genetics and other functional information. MalaCards is an integrated database of human diseases, including information such as diseases and associated comments. The MalaCards disease database presents relevant information in the form of a "disease card". Each "disease card" integrates the priority information and lists the known alias name for each disease, as well as various comments and relationships between diseases as authorized by the GeneCards relational database for searching and genetic analysis. The annotations include: symptoms, drugs, articles, genes, clinical trials, and related diseases/disorders, and the like. The automated computing information retrieval engine populates the "disease card" with remote data, and compiles a disease database using information collected by the GeneCards platform. The MalaCards disease database integrates specialized and general diseases including rare diseases, genetic diseases, complex diseases, and the like.
FIG. 7 is a schematic hierarchical diagram of a rare disease knowledge base management component in accordance with one embodiment of the present invention. As shown in fig. 7, the overall architecture of the rare disease knowledge base management component 111 is divided into: the system comprises a user layer, a display layer, an application layer, a data layer, a database and a hardware layer. Users of the system are divided into three categories: the system comprises a researcher, a common user (such as a patient) and an administrator, wherein the researcher user is a main user, data of a plurality of medical websites are collected for searching, accurate medical platforms, disease knowledge, GeneReviewss, CHPO, GeneCards and MalaCards information are covered, and more effective medical data are provided for the user for reference. The rare disease knowledge base management component 111 quickly jumps to the precise medical platform by utilizing a JavaScript search jump function; uniformly arranging and displaying the disease knowledge by using front-end HTML (hypertext markup language), realizing a full-text retrieval function by using solr, and quickly inquiring related disease knowledge data; the method comprises the steps of showing the whole generalization of the GeneReviewss by utilizing front-end HTML, searching and jumping to a GeneReviewss website by utilizing a JavaScript search jumping function, and quickly inquiring related GeneReviewss data; displaying the overall CHPO summary by using front-end HTML, skipping to a CHPO website by using a JavaScript search skipping function, and quickly inquiring related CHPO data; the method comprises the steps of showing the whole generalization of the GeneCards by using front-end HTML, skipping to a GeneCards website by using a JavaScript search skipping function, and quickly querying related GeneCards data; and jumping to the MalaCards website by utilizing a search jumping function, and quickly inquiring related MalaCards data.
The rare disease case data sharing component 112 obtains case data for each rare disease collected by the researcher client, processes the case data (including but not limited to cleaning, converting, classifying, calculating, etc. of the data), and finally warehouses (i.e., stores the processed case data on the rare disease case database server 105). The rare disease case data sharing component 112 includes a case statistics unit for counting case data of each rare disease and updating the statistical result in real time according to the acquisition situation. On the other hand, the rare disease case data sharing component 112 can transmit the statistical result to the front-end HTML information publishing component 113 to publish on the portal site in time. The front-end HTML information distribution component 113 can display the geographical distribution of case data in the form of map distribution and the age distribution of case data in the form of a graph. Meanwhile, statistics of the number of diseases of men and women can be respectively displayed. The map distribution adopts the ECharts technology and the thermal distribution technology, presents different colors according to different numerical values and is clear for users. The user may download the geo-profile and chart via a web portal.
The front-end HTML information publishing component 113 employs well-established HTML5 technology. The advantages of HTML5 are: increased usability and improved user friendly experience; new tags this will help developers define important content; more multimedia elements (video and audio) can be brought to the site; can well replace FLASH and Silverlight; it is very friendly to SEO when it comes to crawling and indexing of web sites.
The rare disease knowledge database server 104 is used to store rare disease-related knowledge from multiple data sources. The rare disease case database server 105 is configured to store rare disease case statistical data, and includes, for example, a database storing information of each rare disease case and a database storing statistical results of each rare disease case. The metadata repository server 106 is used for storing metadata and dictionaries that are needed by researchers to design research form templates, the metadata including public metadata and private metadata and the dictionaries including public dictionaries and private dictionaries. The database system adopted by the invention can support TB-level data storage, can support more than 5000 concurrent connections and supports mainstream SAN equipment.
In a preferred embodiment, the Web application server 102 also includes a big data analysis unit connected to the rare disease knowledge base management component. The big data analysis unit comprises a calculation unit and a storage unit, wherein the calculation unit comprises a CPU and a GPU. Because the system generates massive data, the research on the data only by means of knowledge reserve and clinical experience of researchers needs great effort and time, and the research process encounters difficulty which cannot be overcome temporarily. Based on the method, the system combines big data analysis and mining technology to carry out deep and accurate analysis on the data, and helps scientific research personnel to efficiently and accurately find related knowledge from massive information to carry out research. The CPU and the GPU are adopted to calculate the structure, the CPU is responsible for executing logical transaction processing and serial calculation, and the GPU is responsible for executing highly threaded parallel processing tasks, so that the calculation capacity is greatly improved.
In addition, the apparatuses, devices and the like disclosed in the embodiments of the present invention may be various electronic terminal devices, such as a mobile phone, a Personal Digital Assistant (PDA), a tablet computer (PAD), a smart television and the like, or may be large terminal devices, such as a server and the like, and therefore the scope of protection disclosed in the embodiments of the present invention should not be limited to a specific type of system or device.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The various illustrative logical blocks, modules, and circuits described herein may be implemented or performed with the following components designed to perform the functions described herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and/or any other such configuration.
Although the invention has been described in detail hereinabove with respect to a general description and specific embodiments thereof, it will be apparent to those skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (10)
1. A rare disease information management system based on a B/S (browser/Server) architecture is characterized by comprising a client, a Web application server and a database server, wherein the Web application server is in communication connection with the client through the Internet, the database server is in communication connection with the Web application server through a switch,
the client side performs data interaction with the Web application server through a Web browser,
the Web application server includes:
a user identity authentication and authority management component;
an audit management component;
a metadata management component;
a form template management component in communicative connection with the metadata management component;
a rare disease knowledge base management component;
a rare case data sharing component; and
a front-end HTML information publishing component communicatively coupled to the rare disease knowledge base management component and the rare disease case data sharing component,
the database server comprises a rare disease knowledge database server, a rare disease case database server and a metadata database server.
2. The B/S architecture-based rare disease information management system of claim 1, wherein the clients comprise a researcher client, a general user client, and an administrator client,
the client of the researcher comprises a user registration information sending unit, a file editing unit, a form template memory, a rare disease data acquisition and transmission unit, and an HTML receiving unit, an HTML analyzing unit and a page display unit which are connected in sequence,
the common user client comprises an HTML receiving unit, an HTML analyzing unit and a page display unit which are connected in sequence,
the administrator client comprises a user registration information sending unit, a data maintenance unit, and an HTML receiving unit, an HTML analyzing unit and a page display unit which are connected in sequence.
3. The B/S architecture-based rare disease information management system of claim 2, wherein the form template storage stores study form templates prepared by researchers for respective rare diseases.
4. The B/S architecture based rare disease information management system of claim 1 wherein the metadata repository server stores metadata and dictionaries that are needed by researchers to perform study form template design, the metadata comprising public metadata and private metadata and the dictionaries comprising public dictionaries and private dictionaries.
5. The B/S architecture based rare disease information management system of claim 1 wherein the rare disease knowledge base management component comprises a database access interface connected to a plurality of medical databases.
6. The B/S architecture based rare disease information management system of claim 5, wherein the plurality of medical databases comprise at least GeneReviewss, CHPO, GeneCards, and MalaCards.
7. The B/S architecture based rare disease information management system of claim 1, wherein the rare disease case data sharing component comprises a case statistics unit.
8. The B/S architecture based rare disease information management system of claim 1, wherein the rare disease knowledge database server stores rare disease related knowledge from a plurality of data sources, the rare disease case database server stores rare disease case statistics.
9. The B/S architecture based rare disease information management system of claim 1 wherein the Web application server further comprises a big data analytics unit connected to the rare disease knowledge base management component.
10. The B/S architecture based rare disease information management system of claim 9, wherein the big data analysis unit comprises a computation unit and a storage unit, the computation unit comprising a CPU and a GPU.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911217905.3A CN110838347A (en) | 2019-12-03 | 2019-12-03 | Rare disease information management system based on B/S framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911217905.3A CN110838347A (en) | 2019-12-03 | 2019-12-03 | Rare disease information management system based on B/S framework |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110838347A true CN110838347A (en) | 2020-02-25 |
Family
ID=69578420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911217905.3A Pending CN110838347A (en) | 2019-12-03 | 2019-12-03 | Rare disease information management system based on B/S framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110838347A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007094943A (en) * | 2005-09-30 | 2007-04-12 | Vitas:Kk | Specific disease medical information management system |
| CN101271489A (en) * | 2008-04-29 | 2008-09-24 | 南京医科大学第一附属医院 | Medicine case information management system |
| CN106845076A (en) * | 2016-12-20 | 2017-06-13 | 杭州联众医疗科技股份有限公司 | A kind of remote image diagnostic system |
-
2019
- 2019-12-03 CN CN201911217905.3A patent/CN110838347A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007094943A (en) * | 2005-09-30 | 2007-04-12 | Vitas:Kk | Specific disease medical information management system |
| CN101271489A (en) * | 2008-04-29 | 2008-09-24 | 南京医科大学第一附属医院 | Medicine case information management system |
| CN106845076A (en) * | 2016-12-20 | 2017-06-13 | 杭州联众医疗科技股份有限公司 | A kind of remote image diagnostic system |
Non-Patent Citations (2)
| Title |
|---|
| 无: "中国国家罕见病注册系统", 《国际药学研究杂志》 * |
| 杨星月: "针灸病例注册登记的方法和关键技术研究", 《中国博士学位论文全文数据库医药卫生科技辑》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Murphy et al. | Serving the enterprise and beyond with informatics for integrating biology and the bedside (i2b2) | |
| US9639662B2 (en) | Systems and methods for event stream platforms which enable applications | |
| Wagholikar et al. | SMART-on-FHIR implemented over i2b2 | |
| Silva et al. | Montra: An agile architecture for data publishing and discovery | |
| Mao et al. | Digital contact tracing based on a graph database algorithm for emergency management during the COVID-19 epidemic: Case study | |
| Hammad et al. | A Semantic‐Based Approach for Managing Healthcare Big Data: A Survey | |
| John et al. | Suicide Information Database-Cymru: a protocol for a population-based, routinely collected data linkage study to explore risks and patterns of healthcare contact prior to suicide to identify opportunities for intervention | |
| Neu et al. | Sharing data in the global Alzheimer's association interactive network | |
| Meeker et al. | A system to build distributed multivariate models and manage disparate data sharing policies: implementation in the scalable national network for effectiveness research | |
| CN113130086A (en) | Health medical big data platform | |
| CN110838370A (en) | Rare disease registration system | |
| Khan et al. | Identifying data sharing and reuse with Scholix: Potentials and limitations | |
| Fu et al. | Design and implementation of clinical LIS360 laboratory management system based on AI technology | |
| Brady et al. | NCI Cancer Research Data Commons: core standards and services | |
| Harris et al. | i2b2t2: unlocking visualization for clinical research | |
| Kounelis et al. | Documentation of clinically relevant genomic biomarker allele frequencies in the next‐generation FINDbase worldwide database | |
| CN110808088A (en) | Rare disease information issuing system based on B/S framework | |
| Ma et al. | Multiple wide tables with vertical scalability in multitenant sensor cloud systems | |
| CN110838347A (en) | Rare disease information management system based on B/S framework | |
| Drezen et al. | From medico‐administrative databases analysis to care trajectories analytics: an example with the French SNDS | |
| Smith et al. | Liaison psychiatry—measurement and evaluation of service types, referral patterns and outcomes (LP-MAESTRO): a protocol | |
| CN110993047A (en) | Rare disease information management method, rare disease information management device and computer-readable storage medium | |
| CN110827943A (en) | Method for researching rare diseases | |
| CN110838369A (en) | System for be used for rare disease research | |
| Branescu et al. | Solutions for medical databases optimal exploitation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200225 |
|
| RJ01 | Rejection of invention patent application after publication |