springboot community hospital medical record management platform
With the advent of the Internet era and the rapid development of computer network technology, network management applications have become more and more widespread. Therefore, establishing a community hospital medical record management platform with a B/S structure will systematize and standardize the medical record management work of community hospitals , improve the image of community hospitals , and improve management efficiency.
This community hospital medical record management platform is aimed at the actual needs of current community hospital medical record management. Based on actual work, it analyzes the problems existing in community hospital medical record management in the past, and combines the structure, concepts, models, principles, and methods of computer systems to Taking advantage of various computer advantages, it is designed and implemented using the most popular springboot framework, B/S structure, Java technology, and MySQL database. This community hospital medical record management platform mainly includes multiple modules such as the implementation of the login module, web page module, administrator module, and supervisory user module . It helps community hospital medical record management achieve informatization and networking. Through testing, it has achieved the system design goals. Compared with the traditional management model, this system makes reasonable use of network data resources and effectively reduces the complexity of the community hospital medical record management platform . Economic investment has greatly improved the efficiency of community hospital medical record management platforms .
Keywords: springboot framework; JAVA programming language; MYSQL database ; community hospital medical record management platform
Springboot Community Hospital Medical Record
Management Platform
With the advent of the Internet era and the rapid development of computer network technology, the application of network management has become increasingly widespread. Therefore, establishing a B/S structured community hospital medical record management platform will systematize and standardize the medical record management work of community hospitals, improve the image of community hospitals, and improve management efficiency.
This community hospital medical record management platform is based on the actual needs of the current community hospital medical record management, starting from the actual work, analyzes the problems existing in the past community hospital medical record management, combines the structure, concept, model, principle and method of the computer system, and uses the most popular springboot framework, B/S structure, java technology, MySQL database design design and implementation under the various advantages of the computer. The medical record management platform of this community hospital mainly includes multiple modules, such as the implementation of login module, webpage module, administrator module, and supervisor user module. It has helped community hospital medical record management achieve informatization and networking. Through testing, the system design goals have been achieved. Compared to traditional management models, this system makes reasonable use of network data resources, effectively reducing the economic investment of the community hospital medical record management platform, and greatly improving the efficiency of the community hospital medical record management platform.
Keywords: springboot framework; JAVA programming language; MYSQL database; Community Hospital Medical Record Management Platform
Table of contents
Chapter 2 Technology and Principles
2.1 Introduction to spring boot framework
Chapter 5 System Implementation
5.1 Implementation of login module
5.2 Front-end user function module
5.4 Supervisor user function module
6.1 Basic concepts of program testing
6.2 Specific contents of program testing
6.2.1 Importance and purpose of testing
Chapter 1 Introduction _
1.1 Development background
In the rapidly developing information age , more and more Internet technologies have entered people's lives . People have begun to accept the convenient and fast services brought by the Internet , and at the same time enjoy the impact and impact brought by the Internet. The community hospital medical record management platform is an indispensable management website for hospital management at present , but due to various unpredictable practical reasons, it cannot be universally implemented . If it takes a long time, the management will be very inconvenient, there will be errors, and it will be difficult to query. Once there is too much data, it will be difficult to maintain the manual management method. With the expansion of the application of information technology, information technology management has been gradually introduced, gradually replacing the manual management model, and using computer systems to manage hospital information. Intelligent management reduces human, material and financial resources , saves management time and space , and improves efficiency. accuracy and efficiency of work. This system development mainly targets the community hospital medical record management platform , and completes the functional design according to needs.
1.2 Development significance
Users often have a lot of troubles because they cannot make an appointment with their favorite doctor in time. On the other hand, the community hospital medical record management platform failed to carry out systematic management and maintenance, resulting in the failure of doctors, departments, and medical record information to be updated in a timely manner. However, traditional community hospital medical record management still uses manual filing and manual query. However, as the number of people increases, the workload of this management method continues to increase. This approach has the disadvantages of being time-consuming and labor-intensive, lacking in timeliness, and not conducive to mobilizing the enthusiasm of personnel. Once the website is established, on the one hand, users can query the required information in the system immediately; on the other hand, the system can also manage the information, reducing the workload of manual processing.
This community hospital medical record management platform management system is established to facilitate users to query the information they need through the entry and release of information by managers. Once the information they need is queried, users can obtain the information from the system. for easy viewing online . If you do not find the information you need, you can also remind the manager to add it. In this way, this system aims to establish a bridge relationship between competent users and managers, so that users can present information from managers in a timely and effective manner. Therefore, we believe that it is very necessary to establish an online community hospital medical record management platform management system. Its convenient, efficient, simple and fast management mode is very useful.
1.3 Research content
Login issues for different users : Differentiate administrator operation permissions and display different operation interfaces based on user information (administrator, supervisory user).
Database connection issues: Database connection is a key technology in the system.
Data consistency and security issues: This system must ensure data consistency and security in order to achieve effective management. Do not allow administrators without permission to operate on the data and back up the database regularly.
Interface development: The design of the system interface is very important to make the interface friendly.
Analyze the current status of informatization;
Study the current status and existing problems of community hospital medical record management platforms ;
Research the overall architecture, overall design, database design, database security design and functional design of the system platform;
Research the functions and implementation methods of each subsystem of the platform, the integration of information technology, and the maintenance of information security technology; carry out functional design of the community hospital medical record management platform .
Chapter 2 Technology and Principles
2.1 Introduction to spring boot framework
The Spring framework is an open source application framework on the Java platform that provides a container with control inversion characteristics. Although the Spring framework itself has no restrictions on the programming model, its frequent use in Java applications made it so popular that it was later used as a supplement or even a substitute for the EJB (Enterprise JavaBeans) model. The Spring framework provides a series of solutions for development, such as utilizing the core features of inversion of control and implementing inversion of control through dependency injection to implement containerization of the managed object life cycle, using aspect-oriented programming for declarative transaction management, and integration A variety of persistence technologies manage data access, provide a large number of excellent web frameworks to facilitate development, and so on. The Spring framework has the Inversion of Control (IOC) feature. IOC is designed to facilitate project maintenance and testing. It provides a method for unified configuration and management of Java objects through Java's reflection mechanism. The Spring framework uses containers to manage the life cycle of objects. The container can configure objects by scanning XML files or specific Java annotations on classes. Developers can obtain objects through dependency lookup or dependency injection. Spring framework has aspect-oriented programming(AOP) framework, the Spring AOP framework is based on the proxy mode and is configurable at runtime; the AOP framework mainly modularizes cross-concerns between modules. The AOP framework of the Spring framework only provides basic AOP features. Although it cannot be compared with the AspectJ framework, it can also meet basic needs through integration with AspectJ. Transaction management, remote access and other functions under the Spring framework can be realized by using Spring AOP technology. Spring's transaction management framework brings an abstraction mechanism to the Java platform that enables local and global transactions, as well as nested transactions, to work with savepoints and in almost any environment on the Java platform. Spring integrates a variety of transaction templates. The system can configure transactions through transaction templates, XML or Java annotations, and the transaction framework integrates functions such as messaging and caching. Spring's data access framework solves common difficulties developers encounter when using databases in their applications. It not only provides support for all popular data access frameworks such as Java: JDBC, iBATS/MyBATIs, Hibernate, Java Data Objects (JDO), ApacheOJB and ApacheCayne, but can also be used with Spring's transaction management to provide data access. Flexible abstraction. The Spring framework did not initially intend to build its own Web MVC framework . During the development process, its developers believed that the separation between the presentation layer and the request processing layer of the existing StrutsWeb framework, as well as between the request processing layer and the model, was not enough, so they created SpringMVC.
2.2 JAVA technology
The Java language is currently the most commonly used language program, and its code is open source and can be used by any software developer. It has already had a profound impact on the history of human computer programming language development. Therefore, the Java language is very mature. It is a good choice to apply it to the development of our system, and because it is common, most people can operate it.
The Java language has a variety of features. It is very simple to write code and has a variety of writing methods. It is very object-oriented, and it does not have any requirements for the platform it is used. All platforms can be used. Operation, its safety performance is also very high, so it is very suitable for the development of this system.
Java does not have any platform requirements and can be run on any platform. It can start running without the need to use other language editors to edit the code. This is very good, not only the ones we are using It is more convenient and can be implemented without the help of other programs, so it can save our development costs. Moreover, the program code edited by Java can be used directly without recompiling, so it is very convenient. Moreover, the application of the program does not require professional skills to run, which provides great feasibility for software development.
2.3 MySQL database
The mysql database has many advantages. It is very simple to operate. You only need to write a small piece of code to achieve the corresponding functions, and the written code can be used on any platform. There are no requirements for the use of the platform. Therefore Any software developer can use the mysql database to develop and design the system. At the same time, it can also save a lot of overhead for software development. The mysql database has large storage capacity and simple operation. It is so powerful that it is completely possible to use it as the data storage of this system.
The mysq database is an open architecture that can be used by any software developer. With the continuous development of computer networks, the MySQL database is constantly improving in terms of functionality and is more suitable for the development of all systems. We are improving the database When operating, it is very simple and easy to use. We only need to write a small piece of code to achieve the corresponding function, and the edited code can be used on any platform without the need for secondary compilation. Because the MySQL database has many of the above advantages, we use it as the first choice for database application in system development. Because its size is very small and the cost of development is also very low, it is loved by many software developers and is more popular. Most of them are used in the opening of the system, so this system also uses the MySQL database to store and edit all data.
2.4 B/S structure
The B/S (browser/server) structure is currently the most commonly used structural model. It can make system development simpler, easier to operate, and can also be maintained. When using this structure, you only need to install a database in your computer and some commonly used browsers. The browser will connect the information with the database, which can realize many functions. The B/S structure can be used directly, and the B/S structure greatly reduces the maintenance work during use. Based on B/S software, all databases are independent of each other, so they are very safe. Because based on the B/S structure, you can clearly see the business being processed by the system, and allow managers to make decisions in a timely manner, thus avoiding corporate losses. The basic feature of the B/S structure is the centralized management model. After users use the system to generate data, the data can be stored in the system's database for future use, thus meeting all people's needs.
Figure 2-1 Three-layer structure diagram of B/S mode
Chapter 3 System Analysis
3.1 Feasibility analysis
The system designed in this article will conduct a comprehensive feasibility analysis from the aspects of economic feasibility, technical feasibility and operational feasibility.
3.1.1 Economic feasibility
This system is a community hospital medical record management platform. It is aimed at computer users, so the cost is not high. Maintenance and debugging only require the participation of individual members, so the human investment is very small. Although the investment in manpower and capital is not a lot, the gains are very considerable, especially from a long-term perspective. The so-called knowledge is priceless, and custodians need to face a lot of troubles, and the community hospital medical record management platform is largely After solving this problem, in the future, very few people need to be invested in resource storage. It does not require a lot of people. Few people can ensure the security of information, so the funds for personnel can be reduced a lot, and The staff doesn't have a hard time.
The database used is a MySQL database, which is very low cost for small websites and greatly reduces space. The original space can be used to process other things .
3.1.2 Technical feasibility
In terms of technology, it is completely possible. The current technology is enough to develop a complete community hospital medical record management platform. Because the object-oriented approach is relatively single, the technologies required are not complicated. They are all knowledge learned in school, and the tools required are not very complicated either. Using Dreamweaver as the development platform, using Java to write pages and Apache to connect to the database, and using the simplest MySQL database, it is very easy to maintain. This system is based on the B/S structure, which is relatively simple and clear. So it is feasible from a technical perspective .
3.1.3 Operational feasibility
The development of this system uses basic technology and is aimed at a single group, so it will not cause information congestion and collapse, so the user's commands can be executed quickly during runtime. The data that exists on the page will be transferred to the database in the form of a form, so there will be no confusion .
For now, in the era of widespread computer use, it is not difficult to learn to maintain and use the system, so it is feasible in terms of personnel, and the system can be used on different computers, so it can also be run here .
3.1.4 Time feasibility
In terms of time, since the project is not very large, it can be completed within the time frame. But you need to make good time arrangements. Because this graduation project is for a single person, you need to self-monitor and urge, and you must not change your mind. You must first have a clear time plan. In order to complete this system within a limited time
3.1.5 Legal feasibility
The technologies and resources used in this system are all legal, the quoted parts are marked, and the references are in compliance with regulations. They are personal creations and do not involve any behavior that harms the intellectual property rights of others.
3.2 Requirements analysis
In response to existing problems and needs, a digital and information-based community hospital medical record management platform was established through analysis of functional requirements .
This system mainly includes multiple functional modules such as the implementation of the login module, web page module, administrator module, and supervisory user module. The requirements for these functional modules are briefly described below. Different permissions correspond to the requirements of corresponding functional modules. The administrator permission level is the highest, so the corresponding requirements are the most. According to different permissions, the requirements of each permission are briefly explained.
3.3 Business process analysis
Overall business process: As an administrator, enter your account and password on the login page, go through database identity verification, and log in to the system homepage after successful verification. You can use the system, management system and other functions .
The business process of the system is shown in the figure below.
Figure 3-1 System business flow chart
3.4 Data process analysis
Data flow diagram, abbreviated as DFD , uses graphics to illustrate the logical functions of the system and describes the flow direction and logical transformation of system data. Because this method can express difficult-to-explain problems, it is widely used by developers and is currently a structured system analysis method with a wide range of applications.
The zero-layer data process is the most abstract layer in the process. It includes functional modules such as login management, administrator function management, and retrieval and maintenance management. The data used in the login module includes administrator account information documents and administrator information documents. , The storage required by the administrator function management module is for the administrator to add information documents, query information documents, and delete information documents. The retrieval and maintenance is to search through the above document information through keywords.
The layer 1 data flow diagram of the system is shown in the figure below.
Figure 3-2 System data flow diagram (layer 1)
Layer 2 is the background data flow diagram for administrator operations. Administrators can manage system administrators by adding, modifying, and deleting, as shown in the following figure:
Figure 3-4 System data flow diagram ( layer 2 )
Chapter 4 System Design
4.1 System structure design
The system design is mainly for administrators to process related operations of the entire system after logging in, including home page, carousel chart, notification and announcement management, resource management (hospital information, information classification), system users (administrators, supervisory users), and module management. (Medical record information, follow-up reminders, department information, doctor information, drug information, gender ratio, disease ratio, hospitalization information, follow-up information, department name, disease name) and other operational management .
The functional structure diagram of the system is shown in the figure below.
Figure 4-1 System functional structure diagram
4.2 Function module design
System login: System login is the gateway for administrators to access the system. The system login interface is designed, including the administrator name, password and verification code, and then the identity information of the logged-in administrator is determined to determine whether it is an administrator or a supervisory user .
Administrator management: Administrators can manage the accounts of other supervisory users in the system, including entering new administrators, deleting existing supervisory users, modifying the information of existing supervisory users, and searching for supervisors by keywords such as supervisor username and name. User, print the administrator list page and export the administrator list to excel .
Change password: All system administrators (administrators and supervisory users) should be able to change their login passwords, and need to log in again after modification.
Personal information management: Used by supervisory users. After supervisory users log in to the system, they can modify personal original information, such as modifying phone numbers, email addresses, etc. The administrator's administrator name cannot be modified.
Login status management: Each administrator of the system should be able to view personal historical login status, such as login IP , login time, login address, etc., to prevent administrator account theft and strengthen administrator account security.
4.3 Database design
The most critical part of the system is the database, which requires a very clear idea. Therefore, it is necessary to establish the connection between modules from the beginning of the design, so that the connection between tables and the required content in the table can be clearly established. . Another point of designing a database is to reduce the complicated creation of tables, so connection is very important and can greatly reduce duplicate items in the data table. This can ensure the integrity and unity of the data, without causing data errors and duplication, and the data can be protected by database security, which will make users feel more at ease .
4.3.1 ER diagram design
Conceptual design is the key to the entire database design. In the conceptual design stage, the ER model is obtained from demand analysis. The ER diagram identifies the relationship between the functional model and the data model. In the process of extracting and standardizing the subject database, a simplified ER diagram representation method is used to avoid overly complicated and detailed ER diagram representations that affect the intuition and usability of planning. . It is an abstraction and generalization of the real world. It is a powerful tool for database designers to design data. It can conveniently and directly express various semantic knowledge in applications, making it simple, clear and easy for users to understand . The system ER diagram is shown below.
Figure 4-2 System E - R diagram
4.3.2 Database table design
Database tables are an important part of the database. In fact, the database is just a framework, and the database tables are the essence of the database. The database tables of this system are as follows:
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
token_id |
int |
10 |
0 |
N |
Y |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
Y |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
Y |
N |
||
| 4 |
maxage |
int |
10 |
0 |
N |
N |
2 |
Maximum lifespan: Default 2 hours |
| 5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
user ID: |
Table article (article: article for content management system)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
article_id |
mediumint |
8 |
0 |
N |
Y |
Article id: [0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
N |
Y |
Title: [0,125] is used in the title tag of articles and html |
|
| 3 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Article classification: [0,1000] is used to search for articles of the specified type |
| 4 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of clicks: [0,1000000000] Number of people who visited this article |
| 5 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 6 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 7 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 8 |
source |
varchar |
255 |
0 |
Y |
N |
Source: [0,255] Source of article |
|
| 9 |
url |
varchar |
255 |
0 |
Y |
N |
Source address: [0,255] used to jump to the website where the article was published |
|
| 10 |
tag |
varchar |
255 |
0 |
Y |
N |
Tag: [0,255] is used to mark the relevant content of the article. Multiple tags are separated by spaces. |
|
| 11 |
content |
longtext |
2147483647 |
0 |
Y |
N |
Text: the main content of the article |
|
| 12 |
img |
varchar |
255 |
0 |
Y |
N |
cover picture |
|
| 13 |
description |
text |
65535 |
0 |
Y |
N |
Article description |
Table article_type (article classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
Y |
Category ID: [0,10000] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
Display order: [0,1000] determines the order in which categories are displayed. |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 4 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 5 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] describes the role of this classification |
|
| 6 |
icon |
text |
65535 |
0 |
Y |
N |
Category icon: |
|
| 7 |
url |
varchar |
255 |
0 |
Y |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table auth (user rights management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
auth_id |
int |
10 |
0 |
N |
Y |
Authorization ID: |
|
| 2 |
user_group |
varchar |
64 |
0 |
Y |
N |
user group: |
|
| 3 |
mod_name |
varchar |
64 |
0 |
Y |
N |
Module name: |
|
| 4 |
table_name |
varchar |
64 |
0 |
Y |
N |
Table Name: |
|
| 5 |
page_title |
varchar |
255 |
0 |
Y |
N |
page title: |
|
| 6 |
path |
varchar |
255 |
0 |
Y |
N |
Routing path: |
|
| 7 |
position |
varchar |
32 |
0 |
Y |
N |
Location: |
|
| 8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
跳转方式： |
| 9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
是否可增加： |
| 10 |
del |
tinyint |
3 |
0 |
N |
N |
1 |
是否可删除： |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
是否可修改： |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
是否可查看： |
| 13 |
field_add |
text |
65535 |
0 |
Y |
N |
添加字段： |
|
| 14 |
field_set |
text |
65535 |
0 |
Y |
N |
修改字段： |
|
| 15 |
field_get |
text |
65535 |
0 |
Y |
N |
查询字段： |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
Y |
N |
跨表导航名称： |
|
| 17 |
table_nav |
varchar |
500 |
0 |
Y |
N |
跨表导航： |
|
| 18 |
option |
text |
65535 |
0 |
Y |
N |
配置： |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
collect_id |
int |
10 |
0 |
N |
Y |
收藏ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
收藏人ID： |
| 3 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 4 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 6 |
title |
varchar |
255 |
0 |
Y |
N |
标题： |
|
| 7 |
img |
varchar |
255 |
0 |
Y |
N |
封面： |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
comment_id |
int |
10 |
0 |
N |
Y |
评论ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
评论人ID： |
| 3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
回复评论ID：空为0 |
| 4 |
content |
longtext |
2147483647 |
0 |
Y |
N |
内容： |
|
| 5 |
nickname |
varchar |
255 |
0 |
Y |
N |
昵称： |
|
| 6 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 9 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 10 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
表department_information (科室信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
department_information_id |
int |
10 |
0 |
N |
Y |
科室信息ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
department_name |
varchar |
64 |
0 |
Y |
N |
科室名称 |
|
| 5 |
department_photo |
varchar |
255 |
0 |
Y |
N |
科室照片 |
|
| 6 |
release_date |
date |
10 |
0 |
Y |
N |
发布日期 |
|
| 7 |
department_introduction |
longtext |
2147483647 |
0 |
Y |
N |
科室简介 |
|
| 8 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
department_name_id |
int |
10 |
0 |
N |
Y |
科室名称ID |
|
| 2 |
department_name |
varchar |
64 |
0 |
Y |
N |
科室名称 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
disease_name_id |
int |
10 |
0 |
N |
Y |
疾病名称ID |
|
| 2 |
disease_name |
varchar |
64 |
0 |
Y |
N |
疾病名称 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
disease_proportion_id |
int |
10 |
0 |
N |
Y |
疾病比例ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
病历编号 |
|
| 5 |
patient_name |
varchar |
64 |
0 |
Y |
N |
病人姓名 |
|
| 6 |
patient_type |
varchar |
64 |
0 |
Y |
N |
病人类型 |
|
| 7 |
treating_diseases |
varchar |
64 |
0 |
Y |
N |
在治疾病 |
|
| 8 |
count_record |
int |
10 |
0 |
N |
N |
0 |
计数记录 |
| 9 |
record_time |
datetime |
19 |
0 |
Y |
N |
记录时间 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
doctor_information_id |
int |
10 |
0 |
N |
Y |
医生信息ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
doctor_id |
varchar |
64 |
0 |
N |
N |
医生工号 |
|
| 5 |
doctors_name |
varchar |
64 |
0 |
Y |
N |
医生姓名 |
|
| 6 |
doctors_gender |
varchar |
64 |
0 |
Y |
N |
医生性别 |
|
| 7 |
doctors_photo |
varchar |
255 |
0 |
Y |
N |
医生照片 |
|
| 8 |
doctor_title |
varchar |
64 |
0 |
Y |
N |
医生职称 |
|
| 9 |
employment_time |
varchar |
64 |
0 |
Y |
N |
从业时间 |
|
| 10 |
department_name |
varchar |
64 |
0 |
Y |
N |
科室名称 |
|
| 11 |
phone_number |
varchar |
16 |
0 |
Y |
N |
手机号码 |
|
| 12 |
doctor_introduction |
text |
65535 |
0 |
Y |
N |
医生简介 |
|
| 13 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
点赞数 |
| 14 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 15 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 16 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
drug_information_id |
int |
10 |
0 |
N |
Y |
药品信息ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
drug_number |
varchar |
64 |
0 |
Y |
N |
药品编号 |
|
| 5 |
pharmaceutical_images |
varchar |
255 |
0 |
Y |
N |
药品图片 |
|
| 6 |
drug_name |
varchar |
64 |
0 |
Y |
N |
药品名称 |
|
| 7 |
drug_pricing |
int |
10 |
0 |
Y |
N |
0 |
药品定价 |
| 8 |
quantity_of_drugs |
int |
10 |
0 |
Y |
N |
0 |
药品数量 |
| 9 |
drug_introduction |
text |
65535 |
0 |
Y |
N |
药品简介 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
follow_up_information_id |
int |
10 |
0 |
N |
Y |
随访信息ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
病历编号 |
|
| 5 |
patient_name |
varchar |
64 |
0 |
Y |
N |
病人姓名 |
|
| 6 |
patient_type |
varchar |
64 |
0 |
Y |
N |
病人类型 |
|
| 7 |
whether_to_follow_up |
varchar |
64 |
0 |
Y |
N |
是否随访 |
|
| 8 |
count_record |
int |
10 |
0 |
N |
N |
0 |
计数记录 |
| 9 |
record_time |
datetime |
19 |
0 |
Y |
N |
记录时间 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
follow_up_reminder_id |
int |
10 |
0 |
N |
Y |
随访提醒ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
病历编号 |
|
| 5 |
patient_name |
varchar |
64 |
0 |
Y |
N |
病人姓名 |
|
| 6 |
patient_gender |
varchar |
64 |
0 |
Y |
N |
病人性别 |
|
| 7 |
patient_age |
int |
10 |
0 |
Y |
N |
0 |
病人年龄 |
| 8 |
patient_type |
varchar |
64 |
0 |
Y |
N |
病人类型 |
|
| 9 |
treating_diseases |
varchar |
64 |
0 |
Y |
N |
在治疾病 |
|
| 10 |
next_follow_up |
date |
10 |
0 |
Y |
N |
下次随访 |
|
| 11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
gender_ratio_id |
int |
10 |
0 |
N |
Y |
性别比例ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
病历编号 |
|
| 5 |
patient_name |
varchar |
64 |
0 |
Y |
N |
病人姓名 |
|
| 6 |
patient_gender |
varchar |
64 |
0 |
Y |
N |
病人性别 |
|
| 7 |
patient_type |
varchar |
64 |
0 |
Y |
N |
病人类型 |
|
| 8 |
count_record |
int |
10 |
0 |
N |
N |
0 |
计数记录 |
| 9 |
record_time |
datetime |
19 |
0 |
Y |
N |
记录时间 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hits_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
表hospitalization_information (住院信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hospitalization_information_id |
int |
10 |
0 |
N |
Y |
住院信息ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
病历编号 |
|
| 5 |
patient_name |
varchar |
64 |
0 |
Y |
N |
病人姓名 |
|
| 6 |
patient_type |
varchar |
64 |
0 |
Y |
N |
病人类型 |
|
| 7 |
hospitalization_or_not |
varchar |
64 |
0 |
Y |
N |
是否住院 |
|
| 8 |
count_record |
int |
10 |
0 |
N |
N |
0 |
计数记录 |
| 9 |
record_time |
datetime |
19 |
0 |
Y |
N |
记录时间 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表medical_record_information (病历信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
medical_record_information_id |
int |
10 |
0 |
N |
Y |
病历信息ID |
|
| 2 |
medical_account |
int |
10 |
0 |
Y |
N |
0 |
医护账号 |
| 3 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 4 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
病历编号 |
|
| 5 |
patient_name |
varchar |
64 |
0 |
Y |
N |
病人姓名 |
|
| 6 |
patient_gender |
varchar |
64 |
0 |
Y |
N |
病人性别 |
|
| 7 |
patient_age |
int |
10 |
0 |
Y |
N |
0 |
病人年龄 |
| 8 |
patient_type |
varchar |
64 |
0 |
Y |
N |
病人类型 |
|
| 9 |
date_of_birth |
date |
10 |
0 |
Y |
N |
出生日期 |
|
| 10 |
ethnic_name |
varchar |
64 |
0 |
Y |
N |
民族名称 |
|
| 11 |
phone_number |
varchar |
16 |
0 |
Y |
N |
手机号码 |
|
| 12 |
treating_diseases |
varchar |
64 |
0 |
Y |
N |
在治疾病 |
|
| 13 |
inspection_records |
varchar |
255 |
0 |
Y |
N |
检查记录 |
|
| 14 |
image_recording |
varchar |
255 |
0 |
Y |
N |
影像记录 |
|
| 15 |
hospitalization_or_not |
varchar |
64 |
0 |
Y |
N |
是否住院 |
|
| 16 |
hospitalization_records |
text |
65535 |
0 |
Y |
N |
住院记录 |
|
| 17 |
whether_to_follow_up |
varchar |
64 |
0 |
Y |
N |
是否随访 |
|
| 18 |
follow_up_records |
text |
65535 |
0 |
Y |
N |
随访记录 |
|
| 19 |
next_follow_up |
date |
10 |
0 |
Y |
N |
下次随访 |
|
| 20 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 21 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 22 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
公告id： |
|
| 2 |
title |
varchar |
125 |
0 |
N |
N |
标题： |
|
| 3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文： |
|
| 4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
praise_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
status |
bit |
1 |
0 |
N |
N |
1 |
点赞状态:1为点赞，0已取消 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
slides_id |
int |
10 |
0 |
N |
Y |
轮播图ID： |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题： |
|
| 3 |
content |
varchar |
255 |
0 |
Y |
N |
内容： |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
链接： |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
轮播图： |
|
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量： |
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
supervisor_user_id |
int |
10 |
0 |
N |
Y |
主管用户ID |
|
| 2 |
medical_name |
varchar |
64 |
0 |
Y |
N |
医护姓名 |
|
| 3 |
medical_gender |
varchar |
64 |
0 |
Y |
N |
医护性别 |
|
| 4 |
department_name |
varchar |
64 |
0 |
Y |
N |
科室名称 |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
上传ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
文件名 |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
访问路径 |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
文件路径 |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
显示顺序 |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
父级ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
文件夹 |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
文件类型 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
用户ID：[0,8388607]用户获取其他与用户相关的数据 |
|
| 2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
账户状态：[0,10](1可用|2异常|3已冻结|4已注销) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
所在用户组：[0,32767]决定用户身份和权限 |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
上次登录时间： |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
手机号码：[0,11]用户的手机号码，用于找回密码时或登录时 |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
手机认证：[0,1](0未认证|1审核中|2已认证) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
用户名：[0,16]用户登录时所用的账户名称 |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成 |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱：[0,64]用户的邮箱，用于找回密码时或登录时 |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证：[0,1](0未认证|1审核中|2已认证) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID：[0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序：[0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
名称：[0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该用户组的特点或权限范围 |
|
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
第5章 系统实现
5.1登录模块的实现
系统登录模块可分为前台登录模块和后台登录模块，为确保系统安全性，系统操作员只有在登录界面输入正确的管理员名、密码、权限以及验证码，单击“登录”按钮后才能够进入本系统的主界面。
管理员登录流程图如下所示。
图5-1管理员登录流程图
登录界面如下图所示。
5.2前台用户功能模块
首页，用户进入前台网页，可以查看首页、通知公告、医院资讯、科室信息、医生信息、药品信息、我的等模块内容，如图5-3所示。
图5-3前台首页界面图
通知公告，在通知公告页面中可以查看通知公告详情信息，如图5-4所示。
图5-4通知公告界面图
医院资讯，用户登录后可在医院资讯页面中可以查看资讯详情信息，并可进行点赞、收藏、评论等操作，如图5-5所示。
图5-5医院资讯界面图
病历信息，用户登录后可在病历信息页面中可以查看病历信息详情，可根据关键搜索相关病历，进行影像记录、检查记录下载等操作，如图5-6所示。
图5-6病历信息界面图
5.3 管理员模块
管理员登录进入社区医院病历管理平台之后，就可以对所有的信息进行查看，可以查看到首页、轮播图、通知公告管理、资源管理（医院资讯、资讯分类）、系统用户（管理员、主管用户）、模块管理（病历信息、随访提醒、科室信息、医生信息、药品信息、性别比例、疾病比例、住院信息、随访信息、科室名称、疾病名称）等，并且还可以对其进行相应的操作管理，如图5-7所示。
图5-7管理员功能界面图
轮播图管理，在轮播图管理页面中管理员可以添加、修改。删除轮播图内容，如图5-8所示。
图5-8轮播图管理界面图
随访信息管理，在随访信息管理页面中可以查看医护账号、医护姓名、病历编号
、病人姓名、病人类型、是否随访、计数记录、记录时间等信息，还可以根据需要进行修改或删除等操作，如图5-9所示。
图5-9随访信息管理界面图
医生信息管理，在医生信息管理页面中可以查看医生工号、密码、医生姓名、照片、性别、科室、职称等信息，还可以根据需要进行修改或删除等操作，如图5-10所示。
图5-10医生信息管理界面图
5.4主管用户功能模块
主管用户点击后台进入到系统操作界面，可以查看首页、模块管理（病历信息、随访提醒、科室信息、医生信息、药品信息、性别比例、疾病比例、住院信息、随访信息、科室名称、疾病名称）等信息，如图5-11所示。
图5-11主管用户功能界面图
病历信息管理，在病历信息管理页面主管用户可以添加、提交医护账号、医护姓名、病历编号、病人姓名、病人性别、病人年龄、病人类型、出生日期、民族名称、手机号码、在治疾病、检查记录等信息，并可进行查看、修改、删除等操作，如图5-12所示。
图5-12病历信息管理界面图
科室信息管理：在科室信息管理页面可以添加、提交医护账号、医护姓名、科室名称、科室照片、发布日期、科室简介等信息，并可以进行查看、修改、删除等操作，如图5-13所示。
图5-13科室信息管理界面图
检查信息：在检查信息页面通过填写索引、检查编号、项目名称、项目类型、检查报告、检查时间、医生工号、医生姓名、账号、姓名、就诊卡号等信息进行修改，如图5-14所示。
图5-14检查信息界面图
疾病名称管理，在疾病名称管理页面可以查看疾病名称、创建时间、更新时间等信息，并可进行详情操作，如图5-15所示。
图5-15疾病名称管理界面图
第6章 系统测试
6.1 程序测试基本概念
程序测试是很重要的一个环节，当自身的程序已经完成时，仍需要测试来保证程序的正确性和可靠性，因为往往此时出现的错误就是用户可能会出现的错误，所以调试变得至关重要。唯有经过多次的调试才能够使系统达到完美的状态，使得用户可以安全，放心的使用程序，保障用户信息的安全是每个系统最基本的需求，因而调试也就是系统的最基本的要求。但是为了保证说最大程度减少开发者的工作量，应当分三个阶段来测试，初期，中期和最终期。前期：主要调试模块间的关系部分，看看是否是正确的，合理的，否则到后面会造成难以修改和总是出错的现象。中期：插入部分数据，看看是否数据库方面连接和设计得当，有些时候理念存在的是不能够在现实中完美实现的，并且调试界面找到最优的布局。最终期：插入全部数据，看是否正确，修改页面看是否能达到最初预期效果，检查功能是否完全实现。
6.2 程序测试具体内容
6.2.1 测试的重要性及目的
1.测试的重要性
只有经过反复的测试，才能够使系统得到最稳定的状态，才能把最好的一面展现给使用的用户，是极为关键的一个步骤。但是往往也是大家极容易忽视的一个部分，因为绝大部分的人认为这个部分是不重要的，但事实并非如此，任何系统不管怎样做都不可能完全去除错误，所以需要测试来最大程度的降低和减少错误。要在多环境下进行测试，以保证用户能够在不同环境配置下都能够正常使用。大多数，用户的需求是不断更新的，所以测试具有十分重要的意义，能够及时的把握到用户的最新动态，做出对系统的修改。
测试的目的
测试是为了让用户能够使用到系统的最好一面，能够充分利用到系统内的跟自己相关的部分。另一方面，从系统开发者的角度来说，这个举措有助于开发者在开发系统的同时能够与用户保持有好的关系，能够使开发的系统减少最多的错误和误差，并且有助于开发，边测试边开发，能够及时解决用户的需求，而开发者也能够减少返工的工作量，保证开发是朝着正确的道路前进的，并且对于用户来说能够定期看到一定的工作成果，也是更有助于提出更好的意见，而不是到末期突然提出大量的工作需求。这样可以使得用户和开发者之间的关系得到一定程度的改善，而开发者也从中得到更多改善系统的方向。
6.2.2登录测试
登录及管理员添加模块是对各个系统中不可缺少的功能之一，为了对在运行过程能正常的操作本项目就要对此进行测试。
1. 使用不同浏览器访问服务器的IP地址。
2. 输入特殊的信息登录系统，例如边界值等。
3. 查看登录及管理员添加之后登录系统所返回的结果。
无论系统管理员还是用户登录时都需要用户名和密码进行登录，当输入正确的用户名和密码观察是否正常登录。登录测试表如下表6-1所示：
表6-1登录测试表
| 名称 |
功能名称 |
操作阐述 |
期盼结果 |
测试结果 |
| 登录信息管理 |
登录 |
系统管理员登录时输入 账号：admin密码：admin |
进入后台主页面 |
成功 |
| 添加用户登录时输入 账号：zhangchao密码：000000 |
进入系统首页 |
成功 |
管理员可以管理添加用户的信息。添加测试表如下表6-2所示：
表6-2添加测试表
| 名称 |
功能名称 |
操作阐述 |
期盼结果 |
测试结果 |
| 添加信息管理 |
添加 |
管理员进入添加用户管理页面 |
成功显示所有添加用户列表 |
成功 |
| 管理员进入添加用户管理页面，点击删除按钮 |
删除成功，出现删除成功的提示 |
成功 |
||
| 用户进入添加页面，按提示输入添加用户信息 |
添加成功，出现添加成功的提示 |
成功 |
6.2.3用户管理模块测试
用户管理信息模块对本界面中的数据和信息进行相对应得基本操作，主要有查看用户，删除用户等。
管理员可以查看并删除用户，如表6-3所示：
表6-3用户管理测试表
| 模块名称 |
功能名称 |
操作描述 |
预期结果 |
测试结果 |
| 用户信息管理 |
查看 |
管理员进入用户管理页面，查看用户 |
所有用户均显示 |
成功 |
| 删除 |
管理员进入用户管理页面，点击删除按钮 |
弹窗提示，删除成功 |
成功 |
6.3 系统的优点
本系统的优点在于界面简单，对于有计算机基本操作的人群均可以高效的使用，查询功能可以使使用者在大量的数据搜索时能够快速的找到所需要的内容，开发的结构简单所以便于日后进行维护和更新功能。信息的添加和查询，使得资源得到了充分的利用。功能并不复杂所以执行速度也较快，所以用户可以得到比较良好的体验，系统内部的增删改查也比较人性化，所以比较快捷和精准。用户为管理员用户，而身份而判别使得系统比较明了，更具有安全性，系统内的数据是得到了一定的保护的。而页面上添加用户，新增添了的一个优势在于，添加后的用户，需得到管理员的审核才能够使用，避免了恶意添加或是恶意进入用户内部的举动。并且管理员据有最高权限，保证数据的安全。
第7章 总结
经过几个月的努力还坚持，社区医院病历管理平台终于完成了，程序功能模块能按照需求来运行，能实现多管理员的迸发使用，但是系统由于设计经验以及旅行团知识的局限性，在本系统的开发过程中，在一些功能方面和业务逻辑方面做得不是很完善，系统还存在一些缺陷。界面的设计从布局到外观，受限于自身的设计功底较低，没能达到自己所要设计的界面要求，另一方面，系统存在一些没有考虑的问题和模块。
在学习的过程中首次进行独立设计工作,编码过程出现了许多问题和困难，原以为正确无误的程序运行过程中不会遇到问题，但是在运行过程中也总会出现各种各样的问题，在调试过程中找不出运行出错的原因。而这些基本问题却都是一些简单的问题，例如标点符号应该是英文状态下的，却因为不好的编程习惯造成了一些中文的符号输入，经过仔细观察和老师的帮组下，还是将问题解决了。
目前系统的功能比较简单，还存在许多瑕疵，这是一份遗憾，也是促进我不断进步的动力。
致 谢
经历了近三个多月的动手实践及老师辛勤的指导和同学朋友热心的帮助下，本人的毕业设计社区医院病历管理平台的基本功能也基本完成。
此次设计中，通过不断的探讨与学习使我熟悉、使我初步了解了JAVA相关技术。做的是一个B/S结构的社区医院病历管理平台，使我对做网站所需要，及运行的环境有了初步的了解，在此次设计中我翻阅了较多的书籍，在有限的时间了丰富了对社区医院病历管理平台技术的知识也积累了少许的经验。起初对JAVA的初步认识，通过这次设计更进一步的了解了其工作原理，懂得了配置服务器环境，连接数据库源，在设计过程中，也学会了用dreamweaver设计一个简单的页面，增强了动手的能力，激发了在此方面的兴趣。
但是由于时间、基础及缺乏实践等多方面的问题，还有诸多需要解决的问题依然存在，设计中很多方面考虑不够周全或者考虑不到。
非常感谢我的老师，我的同学，我的朋友并希望在今后的学习生活中不断陪养多方面的兴趣，不断学习进步从而能够实现独立完成。设计中存在的诸多缺点诚肯老师的原谅。
[1]银莉,杜啸楠.基于SpringBoot和Vue的社区服务平台设计与实现[J].电子技术,2022,51(12):182-183.
[2]倪叶枫.现代医院管理会计实践和发展研究[J].投资与创业,2022,33(23):59-61.
[3]李佳俊,何玥,钱嵩橙,李龙飞.“互联网+”背景下基于B/S的云教育系统设计[J].软件,2022,43(10):173-177.
[4]李乐.Java语言应用研究[J].智慧中国,2022(09):80-81.
[5]孙鹏,吴长海,杨凯.人工智能在医院管理中的应用[J].财经界,2022(25):75-77.DOI:10.19887/j.cnki.cn11-4098/f.2022.25.027.
[6]郭娜,王静成,柏斗胜,耿平.互联网+视阈下现代医院管理培训路径探索[J].江苏卫生事业管理,2022,33(05):653-657+670.
[7]薛宾田.基于SpringBoot的星级党员考评系统[J].电脑编程技巧与维护,2022(05):54-56+77.DOI:10.16184/j.cnki.comprg.2022.05.023.
[8]谭梦,刘玉秀,王修来,高天航,谭挺,苏皖.国外医院管理的研究热点分析[J].医学研究生学报,2022,35(04):414-417.DOI:10.16571/j.cnki.1008-8199.2022.04.015.
[9]王南.Java编程在计算机应用软件中的应用特征与技术研究[J].信息记录材料,2022,23(04):130-132.DOI:10.16009/j.cnki.cn13-1295/tq.2022.04.057.
[10]杨迎.Java语言异常处理机制的分析[J].电子技术,2022,51(03):42-43.
[11]曹嵩彭,王鹏宇.浅析Java语言在软件开发中的应用[J].信息记录材料,2022,23(03):114-116.DOI:10.16009/j.cnki.cn13-1295/tq.2022.03.009.
[12]梁秀俊,刘璐,刘彦丰,李斌.基于Java语言的在线导热实验虚拟仿真软件开发[J].实验室研究与探索,2022,41(02):106-110.DOI:10.19927/j.cnki.syyt.2022.02.023.
[13]丁海洋,王昊翔,姚全珠.基于MVVM框架的汽车销售管理系统设计与实现[J].电子制作,2021(22):55-56+8.DOI:10.16589/j.cnki.cn11-3571/tn.2021.22.019.
[14]周常志,甘恒.基于SpringBoot的智慧就业服务平台的设计与实现[J].电脑知识与技术,2021,17(28):182-184+187.DOI:10.14004/j.cnki.ckt.2021.3040.
[15]巢晟盛.基于SpringBoot微服务架构下前后端分离的MVVM模型浅析[J].电脑知识与技术,2021,17(23):128-129+141.DOI:10.14004/j.cnki.ckt.2021.2412.
[16]李俊甲.基于JAVA的文字速录系统的设计与实现[J].信息与电脑(理论版),2021,33(13):94-96.
[17]Fuyuan Cheng. Talent Recruitment Management System for Small and Micro Enterprises Based on Springboot Framework[J]. Advances in Educational Technology and Psychology,2021,5(2).
[18]刘子凡,郭昱君.基于SpringBoot+Mybatis的个人博客系统设计与实现[J].现代信息科技,2021,5(08):104-107+111.DOI:10.19850/j.cnki.2096-4706.2021.08.029.
[19]邓斯妮,陈家敏,蔡维晟,叶开平.基于SpringBoot技术的综测N服务管理系统设计与实现[J].现代信息科技,2021,5(05):13-18.DOI:10.19850/j.cnki.2096-4706.2021.05.003.
[20]Jian Chen,Chen Jian,Pan Hailan. Design of Man Hour Management Information System on SpringBoot Framework[J]. Journal of Physics: Conference Series,2020,1646(1).
Please follow and like + privately message the blogger to receive the project source code for free