Springboot nursing home management system
Summary
With the rapid development of science and technology, all aspects of society and all walks of life are striving to integrate with modern advanced technology and improve their own advantages through scientific and technological means. Of course, nursing home management systems cannot be excluded. The nursing home management system is a management system built with practical application as the development background, using software engineering development methods, and using Java technology. The entire development process first conducts a requirements analysis on the software system to derive the main functions of the system. Then carry out the overall design and detailed design of the system. The overall design mainly includes the overall structure design of the system, the system data structure design, the system function design and the system security design, etc. The detailed design mainly includes the key codes for module implementation, system database access and the specific implementation of the main functional modules. Finally, the system is functionally tested, and the test results are analyzed and summarized to promptly improve the deficiencies in the system, which facilitates future system maintenance and provides reference and help for the development of similar systems in the future.
The database used in this nursing home management system is Mysql, which is developed using JAVA technology. During the design process, the system code was fully guaranteed to have good readability, practicality, easy scalability, versatility, easy later maintenance, easy operation, and simple page.
Keywords : nursing home management system; database; springboot
Springboot Nursing Home Management System
Abstract
With the rapid development of science and technology, all aspects of society and all walks of life are striving to integrate with modern advanced technology and improve their advantages through scientific and technological means. Of course, the management system of nursing homes cannot be excluded. The nursing home management system is a management system built using Java technology, using software engineering development methods, and based on practical application as the development background. The entire development process begins with a requirements analysis of the software system to obtain the main functions of the system. Then, the overall design and detailed design of the system are carried out. The overall design mainly includes the overall system structure design, system data structure design, system function design, and system security design. The detailed design mainly includes the key code for module implementation, system database access, and the specific implementation of the main functional modules. Finally, a functional test of the system was conducted, and the test results were analyzed and summarized to timely improve the shortcomings of the system, providing convenience for future system maintenance and providing reference and assistance for the development of similar systems in the future.
The database used in this nursing home management system is MySQL, developed using JAVA technology. During the design process, the system code has been fully guaranteed to have good readability, practicality, scalability, versatility, ease of later maintenance, easy operation, and concise pages.
Key words:Nursing home management system; database springboot
Table of contents
1.3 Organizational structure of this article
2 System introductionTool information
2.3 springboot frame arrangement
2.4 B/S system working principle
3.1.1 Technology availability 6
3.2.1System development process 7
3.2.3 System operation process
3.2.4 Additional information flow
3.2.5 Revision information flow
3.2.6 Removal information flow
3.3.1AdministratorExample image
3.3.3Meal staffExample picture
4.3.1 Database design principles
5.2Use management interface 30
5.3 department management interface 31
5.4Payment management interface 31
5.5Bed position information management interface 32
5.7 Elderly information management interface 35
6.1The significance of system testing
结论4 0
achie谢4 1
1 Overview
1.1Research Background
nursing home is a comprehensive nursing home that integrates elderly care, nursing and other services. After our preliminary investigation, we found that most of the work in the hospital is done manually, which will cause Problems of low work efficiency and excessive operating costs.
The hospital can achieve better service results with less reasonable investment. While meeting social needs and paying attention to social benefits, it can also obtain corresponding economic benefits, thereby improving the hospital's long-term development capabilities, enhancing internal control capabilities, and improving human and financial management. , obtain more and better methods and means for the comprehensive operation and management of materials, and use limited resources to obtain the most reasonable social and economic benefits.
The nursing home management system realizes the main functions of the system: homepage, user management (administrators, nursing staff, catering staff, financial staff, elderly users, family users), department management, nursing attendance, catering attendance, financial attendance, nursing leave, meal leave, finance Leave requests, bed information, elderly information, health assessment, health records, meal information, charging information, financial income, financial expenditures. The internal management system of the nursing home is centered on the comprehensive management of the hospital's people, finances and materials, and has functions such as intelligent analysis of management decisions. The system adopts an integrated operation model, which can be used as an effective means to improve the hospital's comprehensive operational capabilities.
1.2opening intention
Nursing homes play an indispensable and important role in caring for the physical and mental health of the elderly and providing necessary social assistance. Like other enterprises in society, nursing homes also need high-efficiency and high-standard management systems to achieve the goal of serving the majority of elderly customers. To provide a high level of service. The current status and existing problems of nursing homes include the following two aspects: 1. The information base is weak. The current information collection of some basic information in nursing homes is insufficient to meet the needs of information sharing, statistics, query and other services. 2. Information flow is not smooth. The current transmission of information in nursing homes relies on traditional methods, which lacks efficient circulation and has poor circulation channels.
The scale and diversity of nursing home services have brought challenges to management and service work. For modern nursing homes, traditional management methods have been unable to adapt to the needs of modern nursing homes. However, the use of information-based integrated management can make the management of nursing homes more efficient. Management and service work are more convenient and efficient.
1.3 Organizational structure of this article
The first chapter is the introduction. The beginning of this article provides a textual description of the research background and background of this topic.
Chapter 2 studies the development technologies and development tools used in the nursing home management system.
Chapter 3 is the system analysis part, including description of the overall system requirements, analysis of system requirements from a functional perspective, and non-functional analysis of whether the system can be implemented.
Chapter 4 is the system design part. The important part of this article provides the detailed design of the system architecture and the design instructions of some main functional modules.
Chapter 5 is the specific implementation of the system, introducing the specific implementation of each module of the system.
Chapter 6 builds on the previous chapters to test and run the system.
Finally, a careful summary of the system is given to provide a new outlook for the future.
2 System development environment
2.1 Opening technology
The front-end part of this system is developed based on the MVVM model, using the B/S mode, and the back-end part is developed based on the Java springboot framework.
Front-end part: The front-end framework uses the popular progressive JavaScript framework Vue.js. Use Vue-Router and Vuex to realize dynamic routing and global state management, Ajax to realize front-end and back-end communication, Element UI component library to quickly prototype the page, and the project front-end to achieve responsiveness through grid layout, which can be adapted to PC, tablet, mobile phone, etc. Perfect layout display for different screen sizes.
Back-end part: Use springboot as the development framework, and integrate MyBatis, Redis and other related technologies.
2.2MySQL database
The advancement of science and technology has brought many conveniences to daily life: classroom projectors use virtual imaging technology, and digital cameras use photoelectric detection technology. For example, the records of supermarket goods entering and leaving the warehouse require an information warehouse. This information warehouse is the database, and this logistics information management system also needs the support of this technology [7].
The software MySQL is used because it can accept access from multiple users, and Archive etc. exist in it. It will first classify the data and then save it in tables respectively. Such special operations will improve the speed of the data management system itself and allow the database to be used flexibly. MySQL's code is public and allows others to compile and upgrade it again. This feature can reduce user costs and form a good website system when paired with appropriate software. Although it has shortcomings, in all aspects, it is the mainstream application object of users [8].
2.3Introduction to springboot framework
Spring framework is an open source application framework onJava platform, providing 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 EJB (EnterpriseJavaBeans) model supplement, or even substitute. 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. The Spring framework has an aspect-oriented programming (AOP) framework. The Spring AOP framework is based on the proxy mode and is configurable at runtime; the AOP framework is mainly aimed at the intersection between modules. Focus on modularization. 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 was not originally intended to build its own WebMVC framework. Its developers considered the existing StrutsWeb framework's presentation layer and requests during the development process. There was not enough separation between the processing layers and between the request processing layer and the model, so SpringMVC was created.
2.4B/S system working principle:
The B/S architecture adopts the working mode of browser request and server response.
Users can access text, data, pictures, animations, video on demand, sounds and other information generated by Web servers on the Internet through a browser;
Each Web server can be connected to the database server in various ways, and a large amount of data is actually stored in the database server;
Download the program from the Web server to the local for execution. If you encounter instructions related to the database during the download process, the Web server will hand it over to the database server for interpretation and execution, and return it to the Web server, and the Web server will return it to the user. In this structure, many networks are connected together to form a huge network, that is, the global network. Each enterprise can build its own Internet based on this structure.
In the B/S mode, the user requests access through the browser to many servers distributed on the network. The browser's request is processed by the server, and the processing results and corresponding information are returned to the browser. Other data All processing and requests are completed by the Web Server. Through this framework structure and the browser embedded inside the operating system, this structure has become the mainstream structure pattern of today's software applications.
3 System analysis
The so-called system analysis means that demand personnel obtain information through communication with users, and then put this information through the requirements specification. Presented tousers and developers. In the long history of the development of software functions, for a long time, especially in the beginning, the importance of requirements analysis was not recognized by people. For example, at that time, the American company IBM developed an information management system for British Telecom. Development started without clarity, and the initial construction period was one year. Due to unclear requirements, the construction period was delayed by more than half a year, causing huge losses. This situation also exists in many of our software companies. They develop while developing, and even directly copy the same type of projects without clear communication withusers Making changes will lead to re-changes when the system is accepted, resulting in a huge waste of manpower and material resources. The reason for all these consequences is that the demand acquisition is not timely, unclear, and incomplete.
3.1 Feasibility analysis
Based on nursing home management systemThe main goal is to achieveHome page, department management, nursing attendance, meal attendance, financial attendance, nursing leave, meal leave , financial leave, bed information, elderly information, health assessment, health records, meal information, charging information, financial income, financial expenditure related information management services. After determining the goals, we conduct a feasibility analysis on whether the goals of this system can be achieved from the following four aspects.
3.1.1 Technology availability
Based on nursing home management systemMainly usingspringboot framework, based on B/S structure, Mysql database, The development of applications requires complete functions, simple use, and the establishment of a database with complete, safe and stable data. The development technology based on the nursing home management system is highly feasible, and the developers have mastered certain development technologies, so the development of the system is feasible.
3.1.2 Operational feasibility
The login interface based on the nursing home management system is simple and easy to operate. It uses a common interface window to log in and access the operation through a computer. Members can access it as long as they have used a computer in daily life. operate. The development of this system uses Java language and is based on B/S structure. These development environments make the system more complete. This system has the characteristics of easy operation, easy management, good interactivity, and is very simple in operation. Therefore this system can be developed.
3.1.3 Economic feasibility
Based on nursing home management system is based on B/S mode and uses Mysql database to store data. The required hardware and software environment are easy to purchase on the market. Program development is mainly Development and maintenance of management systems. Therefore, the program does not require high development manpower and financial resources, and the system is not very complex, the development cycle is short, and it has high economic feasibility.
3.1.4 Legal feasibility
Based on nursing home management system is a management system designed by ourselves, which has great practical significance. Because both the software and the database use open source code, the development and design of thissystem does not have any issues such as infringement, and legally Totally feasible.
In summary,Based on the nursing home management system, it is technically, economically, operationally and legally feasible to develop. This procedure is possible.
3.2 System process analysis
3.2.1 System development process
Based on the nursing home management system When developing, first conduct a demand analysis, and then conduct an overall design plan for the system, design system functional modules, database selection, etc., the development process of this system As shown in Figure 3-1
Figure 3-1 System development flow chart
3.2.2 UseRegistration process
In order to ensure the security of the system, if you want to use this system to manage system information, you must first log in to the system. As shown in Figure 3-2.
Figure 3-2 Login flow chart
3.2.3 System operation process
After user opens and enters the system, the login interface will be displayed first, and the correctuser name will be displayed. and password. The system automatically detects the information. If the information is correct, the user will enter the system function interface and perform operations. Otherwise, an error will be prompted and the user cannot log in. Operation process As shown in Figure 3-3.
Figure 3-3 System operation flow chart
3.2.4 Add information process
The administrator can manage department management, nursing attendance, meal attendance, financial attendance, nursing leave, meal leave, financial leave, and bed information , elderly information, health assessment, health files, meal information, charging information, financial income, financial expenditureAdd information, User< a i=5>You can add information within your own authority. After entering the information, the system will verify the entered information and data on its own. If the information is correct, it will be added to the database. If the information is incorrect, it will prompt you to re-enter it. Information, the process of adding information is shown in Figure 3-4.
Figure 3-4 Add information flow chart
3.2.5 Modify information flow
The administrator can manage department management, nursing attendance, meal attendance, financial attendance, nursing leave, meal leave, financial leave, and bed information , elderly information, health assessment, health records, meal information, charging information, financial income, financial expenditureModifications made by usersYou can modify the information within your own authority. First, enter the modification information interface, enter the modification information data, and the system will judge and verify the data. If the modified information is legal, the modification will be successful and the information will be updated to the database. If the information is illegal, the modification will fail and restart. enter. The modified information flow chart is shown in Figure 3-5.
Figure 3-5 Modify information flow chart
3.2.6 Information deletion process
The administrator can manage department management, nursing attendance, meal attendance, financial attendance, nursing leave, meal leave, financial leave, and bed information , elderly information, health assessment, health files, meal information, charging information, financial income, financial expenditureDelete information. After selecting the information to be deleted, click the delete button, and the system will Ask if you are sure. If you click OK, the system will delete the selected information and delete the information in the database. The flow chart of deleting information is shown in Figure 3-6.
Figure 3-6 Deletion information flow chart
3.3 System use case analysis
3.3.1 Administrator use case diagram
The coreuser in the system is thesystem administrator , after the administrator logs in, he can manage the backend system through the administrator menu. The main functions are:Home page, user management, department management, nursing attendance, meal attendance, financial attendance, nursing leave, meal leave, financial leave, bed information, elderly information, health assessment, health files , meal information, charging information, financial income, financial expenditure and other functions. The administrator use case is shown in Figure 3-7.
Figure 3-7 Administrator use case diagram
3.3.2护员工Usage examples
Nursing employeesEnter the system to access the homepagelogin, personal information, nursing attendance, nursing leave, elderly information, health assessment, health records, Nursing resignation functionetc. Nursing staffUsage examples are shown in Figure 3-8.
Picture 3-8 Trial workerUsage example picture
3.3.3Meal staffExample picture
Meal staffEnter the system to access the homepagelogin, personal information, meal attendance, meal leave, elderly information, health assessment, health records, Meal information, meal resignation function, etc. Catering staffUsage examples are shown in Figure 3-8.
Picture 3-9 Food staffExample picture
4 System design
4.1 System Overview
After the system analysis, we begin to memorize system design. System design includes overall design and detailed design. The overall design is just a general design. After the overall design, we can divide some things in the system, such as files, documents, data, etc. And through the overall design, we can roughly divide the modules and functions of the program. But it is only a preliminary classification and has no real implementation.
The overall design is just a preliminary design. Moreover, for a project, we can carry out multiple overall designs. Through comparison, including performance comparison, cost comparison, and benefit comparison, we can finally determine an optimal design plan and choose the best one. The overall design can reduce development costs and increase company benefits. From this point of view, the overall design is still very important.
Based on nursing home management systemThe working principle diagram is shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure design
The system architecture diagram belongs to the system design stage. The system architecture diagram is only a product of this stage. The overall architecture of the system determines the model of the entire system and is the foundation of the system. The overall structural design of the nursing home management system is shown in Figure 4-2.
Figure 4-2 System structure diagram
4.3 Database design
Database is the basis of computer information system. At present, the key and core part of the computer system is the database. The quality of database development has a direct impact on the quality and speed of the entire system.
4.3.1 Database design principles
The conceptual structure design of the database adopts the entity-relationship (E-R) model design method. The constituent elements of the E-R model method are: entities, attributes, and relationships. The E-R model is represented by an E-R diagram, which is a promptuser about things involved in the working environment. Attributes are descriptions of entity characteristics. The database plays a decisive factor in system design. The entity-relationship diagram of these key entities is designed below..
4.3.2 Database entities
Entities in the data model, also called instances, correspond to "events" or "things" that can be distinguished from other objects in the real world.
The E-R diagram of this system is shown below:
1,meal mealProduct image 4-3 Shown:
Picture 4-3Meal menuPractical picture
2, Meal and AttendanceThe entity diagram is shown in Figure 4-4:
Picture 4-4Meal examinationPractical picture
3、护员工实体图郎图4-5Indication:
图4-5劤员工实体图
4.3.3 Database table design
Table bed_information (bed information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
bed_information_id |
int |
10 |
0 |
N |
AND |
Bed information ID |
|
| 2 |
bed_room_number |
varchar |
64 |
0 |
N |
N |
Bed room number |
|
| 3 |
bed_no |
varchar |
64 |
0 |
N |
N |
Bed number |
|
| 4 |
bed_standard |
varchar |
64 |
0 |
AND |
N |
Bed standard |
|
| 5 |
bed_price |
int |
10 |
0 |
AND |
N |
0 |
bed price |
| 6 |
bed_picture |
varchar |
255 |
0 |
AND |
N |
Bed pictures |
|
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table catering_staff (catering staff)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
catering_staff_id |
int |
10 |
0 |
N |
AND |
Meal Employee ID |
|
| 2 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 3 |
employee_gender |
varchar |
64 |
0 |
AND |
N |
Employee gender |
|
| 4 |
employee_age |
varchar |
64 |
0 |
AND |
N |
Employee age |
|
| 5 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 6 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 7 |
date_of_entry |
varchar |
64 |
0 |
AND |
N |
Entry Time |
|
| 8 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table charge_information (charge information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
charge_information_id |
int |
10 |
0 |
N |
AND |
Charge information ID |
|
| 2 |
elderly_users |
int |
10 |
0 |
AND |
N |
0 |
Elderly users |
| 3 |
name_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Old man's name |
|
| 4 |
dependent_users |
int |
10 |
0 |
AND |
N |
0 |
Family users |
| 5 |
family_name |
varchar |
64 |
0 |
AND |
N |
Family name |
|
| 6 |
bed_room_number |
varchar |
64 |
0 |
AND |
N |
Bed room number |
|
| 7 |
bed_no |
varchar |
64 |
0 |
AND |
N |
Bed number |
|
| 8 |
bed_standard |
varchar |
64 |
0 |
AND |
N |
Bed standard |
|
| 9 |
bed_price |
int |
10 |
0 |
AND |
N |
0 |
bed price |
| 10 |
dietary_standards |
varchar |
64 |
0 |
AND |
N |
dietary standards |
|
| 11 |
catering_expenses |
int |
10 |
0 |
AND |
N |
0 |
food expenses |
| 12 |
nursing_expenses |
int |
10 |
0 |
AND |
N |
0 |
care costs |
| 13 |
standards_of_care |
varchar |
64 |
0 |
AND |
N |
standard of care |
|
| 14 |
total_cost |
varchar |
64 |
0 |
AND |
N |
Total cost |
|
| 15 |
pay_state |
varchar |
16 |
0 |
N |
N |
unpaid |
Payment status |
| 16 |
pay_type |
varchar |
16 |
0 |
AND |
N |
Payment type: WeChat, Alipay, online banking |
|
| 17 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 18 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 19 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table department_management (department management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
department_management_id |
int |
10 |
0 |
N |
AND |
Department management ID |
|
| 2 |
department_name |
varchar |
64 |
0 |
AND |
N |
Department name |
|
| 3 |
department_type |
varchar |
64 |
0 |
AND |
N |
Department type |
|
| 4 |
number_of_departments |
varchar |
64 |
0 |
AND |
N |
Department headcount |
|
| 5 |
department_post |
varchar |
64 |
0 |
AND |
N |
Department positions |
|
| 6 |
department_details |
longtext |
2147483647 |
0 |
AND |
N |
Department details |
|
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table dependent_users (family users)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
dependent_users_id |
int |
10 |
0 |
N |
AND |
Family User ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
AND |
N |
username |
|
| 3 |
user_gender |
varchar |
64 |
0 |
AND |
N |
User gender |
|
| 4 |
nursing_age |
varchar |
64 |
0 |
AND |
N |
User age |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table dietary_information (dietary information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
dietary_information_id |
int |
10 |
0 |
N |
AND |
Meal Information ID |
|
| 2 |
elderly_users |
int |
10 |
0 |
AND |
N |
0 |
Elderly users |
| 3 |
name_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Old man's name |
|
| 4 |
age_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Elderly age |
|
| 5 |
height_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man height |
|
| 6 |
weight_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man weight |
|
| 7 |
dependent_users |
int |
10 |
0 |
AND |
N |
0 |
Family users |
| 8 |
family_name |
varchar |
64 |
0 |
AND |
N |
Family name |
|
| 9 |
bed_room_number |
varchar |
64 |
0 |
AND |
N |
Bed room number |
|
| 10 |
bed_no |
varchar |
64 |
0 |
AND |
N |
Bed number |
|
| 11 |
diet_menu |
varchar |
64 |
0 |
AND |
N |
Diet recipes |
|
| 12 |
diet_time |
varchar |
64 |
0 |
AND |
N |
eating time |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table dietary_separation (dietary separation)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
dietary_separation_id |
int |
10 |
0 |
N |
AND |
Meal Separation ID |
|
| 2 |
catering_staff |
int |
10 |
0 |
AND |
N |
0 |
catering staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
application_date |
date |
10 |
0 |
AND |
N |
Date of Application |
|
| 7 |
date_of_resignation |
date |
10 |
0 |
AND |
N |
Resignation date |
|
| 8 |
reason_for_resignation |
varchar |
64 |
0 |
AND |
N |
Reason for leaving |
|
| 9 |
salary_settlement |
int |
10 |
0 |
AND |
N |
0 |
Salary settlement |
| 10 |
salary_details |
text |
65535 |
0 |
AND |
N |
Salary details |
|
| 11 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 12 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table elderly_information (elderly information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
elderly_information_id |
int |
10 |
0 |
N |
AND |
Elderly information ID |
|
| 2 |
elderly_users |
int |
10 |
0 |
AND |
N |
0 |
Elderly users |
| 3 |
name_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Old man's name |
|
| 4 |
age_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Elderly age |
|
| 5 |
height_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man height |
|
| 6 |
weight_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man weight |
|
| 7 |
dependent_users |
int |
10 |
0 |
AND |
N |
0 |
Family users |
| 8 |
family_name |
varchar |
64 |
0 |
AND |
N |
Family name |
|
| 9 |
bed_room_number |
varchar |
64 |
0 |
AND |
N |
Bed room number |
|
| 10 |
bed_no |
varchar |
64 |
0 |
AND |
N |
Bed number |
|
| 11 |
bed_standard |
varchar |
64 |
0 |
AND |
N |
Bed standard |
|
| 12 |
bed_price |
int |
10 |
0 |
AND |
N |
0 |
bed price |
| 13 |
dietary_standards |
varchar |
64 |
0 |
AND |
N |
dietary standards |
|
| 14 |
catering_expenses |
int |
10 |
0 |
AND |
N |
0 |
food expenses |
| 15 |
nursing_expenses |
int |
10 |
0 |
AND |
N |
0 |
care costs |
| 16 |
standards_of_care |
varchar |
64 |
0 |
AND |
N |
standard of care |
|
| 17 |
diet_content |
text |
65535 |
0 |
AND |
N |
Diet content |
|
| 18 |
nursing_content |
text |
65535 |
0 |
AND |
N |
Nursing content |
|
| 19 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 20 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 21 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table elderly_users (elderly users)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
elderly_users_id |
int |
10 |
0 |
N |
AND |
Elderly User ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
AND |
N |
username |
|
| 3 |
user_gender |
varchar |
64 |
0 |
AND |
N |
User gender |
|
| 4 |
nursing_age |
varchar |
64 |
0 |
AND |
N |
User age |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table financial_attendance (financial attendance)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
financial_attendance_id |
int |
10 |
0 |
N |
AND |
Financial Attendance ID |
|
| 2 |
financial_staff |
int |
10 |
0 |
AND |
N |
0 |
Finance staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
attendance_type |
varchar |
64 |
0 |
AND |
N |
Attendance type |
|
| 7 |
attendance_time |
datetime |
19 |
0 |
AND |
N |
Attendance time |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table financial_expenditure (financial expenditure)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
financial_expenditure_id |
int |
10 |
0 |
N |
AND |
Financial expense ID |
|
| 2 |
financial_staff |
int |
10 |
0 |
AND |
N |
0 |
Financial officer |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
date_of_expenditure |
date |
10 |
0 |
AND |
N |
Expenditure date |
|
| 5 |
expense_type |
varchar |
64 |
0 |
AND |
N |
Expenditure type |
|
| 6 |
expenditure_amount |
int |
10 |
0 |
AND |
N |
0 |
amount of payout |
| 7 |
expense_remarks |
text |
65535 |
0 |
AND |
N |
Expenditure notes |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table financial_income (financial income)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
financial_income_id |
int |
10 |
0 |
N |
AND |
Financial Revenue ID |
|
| 2 |
catering_expenses |
int |
10 |
0 |
AND |
N |
0 |
food expenses |
| 3 |
nursing_expenses |
int |
10 |
0 |
AND |
N |
0 |
care costs |
| 4 |
bed_price |
int |
10 |
0 |
AND |
N |
0 |
bed price |
| 5 |
revenue_date |
date |
10 |
0 |
AND |
N |
Income date |
|
| 6 |
financial_staff |
int |
10 |
0 |
AND |
N |
0 |
Financial officer |
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table financial_leave (financial leave)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
financial_leave_id |
int |
10 |
0 |
N |
AND |
Financial Leave ID |
|
| 2 |
financial_staff |
int |
10 |
0 |
AND |
N |
0 |
Finance staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
leave_time |
datetime |
19 |
0 |
AND |
N |
Leave time |
|
| 7 |
end_time |
datetime |
19 |
0 |
AND |
N |
End Time |
|
| 8 |
leave_duration |
varchar |
64 |
0 |
AND |
N |
length of leave |
|
| 9 |
reasons_for_asking_for_leave |
text |
65535 |
0 |
AND |
N |
Reason for leave |
|
| 10 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 11 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table financial_resignation (Financial Resignation)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
financial_resignation_id |
int |
10 |
0 |
N |
AND |
Financial resignation ID |
|
| 2 |
financial_staff |
int |
10 |
0 |
AND |
N |
0 |
Finance staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
application_date |
date |
10 |
0 |
AND |
N |
Date of Application |
|
| 7 |
date_of_resignation |
date |
10 |
0 |
AND |
N |
Resignation date |
|
| 8 |
reason_for_resignation |
varchar |
64 |
0 |
AND |
N |
Reason for leaving |
|
| 9 |
salary_settlement |
int |
10 |
0 |
AND |
N |
0 |
Salary settlement |
| 10 |
salary_details |
text |
65535 |
0 |
AND |
N |
Salary details |
|
| 11 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 12 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table financial_staff (financial staff)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
financial_staff_id |
int |
10 |
0 |
N |
AND |
Finance employee ID |
|
| 2 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 3 |
employee_gender |
varchar |
64 |
0 |
AND |
N |
Employee gender |
|
| 4 |
employee_age |
varchar |
64 |
0 |
AND |
N |
Employee age |
|
| 5 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 6 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 7 |
date_of_entry |
varchar |
64 |
0 |
AND |
N |
Entry Time |
|
| 8 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table health_assessment (health assessment)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
health_assessment_id |
int |
10 |
0 |
N |
AND |
Health Assessment ID |
|
| 2 |
elderly_users |
int |
10 |
0 |
AND |
N |
0 |
Elderly users |
| 3 |
name_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Old man's name |
|
| 4 |
age_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Elderly age |
|
| 5 |
height_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man height |
|
| 6 |
weight_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man weight |
|
| 7 |
dependent_users |
int |
10 |
0 |
AND |
N |
0 |
Family users |
| 8 |
family_name |
varchar |
64 |
0 |
AND |
N |
Family name |
|
| 9 |
bed_room_number |
varchar |
64 |
0 |
AND |
N |
Bed room number |
|
| 10 |
bed_no |
varchar |
64 |
0 |
AND |
N |
Bed number |
|
| 11 |
blood_pressure_range |
varchar |
64 |
0 |
AND |
N |
blood pressure range |
|
| 12 |
heart_rate_range |
varchar |
64 |
0 |
AND |
N |
heart rate range |
|
| 13 |
self_care |
varchar |
64 |
0 |
AND |
N |
Self-care capable |
|
| 14 |
weight_status |
varchar |
64 |
0 |
AND |
N |
weight status |
|
| 15 |
abnormal_blood_pressure |
varchar |
64 |
0 |
AND |
N |
abnormal blood pressure |
|
| 16 |
assessment_details |
text |
65535 |
0 |
AND |
N |
Assessment details |
|
| 17 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 18 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 19 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table health_records (health records)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
health_records_id |
int |
10 |
0 |
N |
AND |
Health Record ID |
|
| 2 |
elderly_users |
int |
10 |
0 |
AND |
N |
0 |
Elderly users |
| 3 |
name_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Old man's name |
|
| 4 |
age_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
Elderly age |
|
| 5 |
height_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man height |
|
| 6 |
weight_of_the_elderly |
varchar |
64 |
0 |
AND |
N |
old man weight |
|
| 7 |
dependent_users |
int |
10 |
0 |
AND |
N |
0 |
Family users |
| 8 |
family_name |
varchar |
64 |
0 |
AND |
N |
Family name |
|
| 9 |
bed_room_number |
varchar |
64 |
0 |
AND |
N |
Bed room number |
|
| 10 |
bed_no |
varchar |
64 |
0 |
AND |
N |
Bed number |
|
| 11 |
blood_pressure_range |
varchar |
64 |
0 |
AND |
N |
blood pressure range |
|
| 12 |
heart_rate_range |
varchar |
64 |
0 |
AND |
N |
heart rate range |
|
| 13 |
self_care |
varchar |
64 |
0 |
AND |
N |
Self-care capable |
|
| 14 |
weight_status |
varchar |
64 |
0 |
AND |
N |
weight status |
|
| 15 |
abnormal_blood_pressure |
varchar |
64 |
0 |
AND |
N |
abnormal blood pressure |
|
| 16 |
historical_illness |
text |
65535 |
0 |
AND |
N |
History of illness |
|
| 17 |
related_medical_genera |
text |
65535 |
0 |
AND |
N |
Related medical |
|
| 18 |
medication |
text |
65535 |
0 |
AND |
N |
Medication status |
|
| 19 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 20 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 21 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table hits (user clicks)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
hits_id |
int |
10 |
0 |
N |
AND |
Like ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Liked by: |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 5 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table leave_for_meals (meal leave)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
leave_for_meals_id |
int |
10 |
0 |
N |
AND |
Meal Leave ID |
|
| 2 |
leave_employee |
int |
10 |
0 |
AND |
N |
0 |
Employees on leave |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
leave_time |
datetime |
19 |
0 |
AND |
N |
Leave time |
|
| 7 |
end_time |
datetime |
19 |
0 |
AND |
N |
End Time |
|
| 8 |
leave_duration |
varchar |
64 |
0 |
AND |
N |
length of leave |
|
| 9 |
reasons_for_asking_for_leave |
text |
65535 |
0 |
AND |
N |
Reason for leave |
|
| 10 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 11 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table meal_attendance (meal attendance)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
meal_attendance_id |
int |
10 |
0 |
N |
AND |
Meal Attendance ID |
|
| 2 |
catering_staff |
int |
10 |
0 |
AND |
N |
0 |
catering staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
attendance_type |
varchar |
64 |
0 |
AND |
N |
Attendance type |
|
| 7 |
attendance_time |
datetime |
19 |
0 |
AND |
N |
Attendance time |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table nursing_attendance (nursing attendance)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
nursing_attendance_id |
int |
10 |
0 |
N |
AND |
Nursing Attendance ID |
|
| 2 |
nursing_staff |
int |
10 |
0 |
AND |
N |
0 |
nursing staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
attendance_type |
varchar |
64 |
0 |
AND |
N |
Attendance type |
|
| 7 |
attendance_time |
datetime |
19 |
0 |
AND |
N |
Attendance time |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table nursing_leave (nursing leave)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
nursing_leave_id |
int |
10 |
0 |
N |
AND |
Nursing leave ID |
|
| 2 |
nursing_staff |
int |
10 |
0 |
AND |
N |
0 |
nursing staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
leave_time |
datetime |
19 |
0 |
AND |
N |
Leave time |
|
| 7 |
end_time |
datetime |
19 |
0 |
AND |
N |
End Time |
|
| 8 |
leave_duration |
varchar |
64 |
0 |
AND |
N |
length of leave |
|
| 9 |
reasons_for_asking_for_leave |
text |
65535 |
0 |
AND |
N |
Reason for leave |
|
| 10 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 11 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table nursing_separation (nursing separation)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
nursing_separation_id |
int |
10 |
0 |
N |
AND |
Nursing separation ID |
|
| 2 |
nursing_staff |
int |
10 |
0 |
AND |
N |
0 |
nursing staff |
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 5 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 6 |
application_date |
date |
10 |
0 |
AND |
N |
Date of Application |
|
| 7 |
date_of_resignation |
date |
10 |
0 |
AND |
N |
Resignation date |
|
| 8 |
reason_for_resignation |
varchar |
64 |
0 |
AND |
N |
Reason for leaving |
|
| 9 |
salary_settlement |
int |
10 |
0 |
AND |
N |
0 |
Salary settlement |
| 10 |
salary_details |
text |
65535 |
0 |
AND |
N |
Salary details |
|
| 11 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 12 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table nursing_staff (nursing staff)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
nursing_staff_id |
int |
10 |
0 |
N |
AND |
Nursing Employee ID |
|
| 2 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 3 |
employee_gender |
varchar |
64 |
0 |
AND |
N |
Employee gender |
|
| 4 |
employee_age |
varchar |
64 |
0 |
AND |
N |
Employee age |
|
| 5 |
employee_department |
varchar |
64 |
0 |
AND |
N |
Staff department |
|
| 6 |
employee_position |
varchar |
64 |
0 |
AND |
N |
Staff positions |
|
| 7 |
date_of_entry |
varchar |
64 |
0 |
AND |
N |
Entry Time |
|
| 8 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
5system统详细设计
5.1registration interface
将首页的左边的功能设计为用户登录的位置，所以在进行登录的地方就会显示首页。在登录后就是大众较为熟悉的位置，也就是让用户进行账号以及密码输入的样式。
当用户输入完信息并点击登录按钮时，Struts就会将用户输入的信息传递进表单并装入相应的对象之中，然后再转到相应位置进行校验。若用户名和密码框都是空的，那么系统就会不可将账号密码均设置为空值。
系统的底层设置要求账号密码不可以都是空值，将这些信息传递给相关的类中的对象方法并调用相关的信息，对于用户输入的数据进行检验。若检验结果正确会自动转到系统首页欢迎页面，如果不正确系统就会返回用户登录界面。
用户登录流程图如下所示。
图5-1 用户登录流程
登录界面如下图所示。
图5-2登录界面图
登录关键代码如下所示。
/**
* 登录
* @param data
* @param httpServletRequest
* @return
*/
@PostMapping("login")
public Map<String， Object> login(@RequestBody Map<String， String> data， HttpServletRequest httpServletRequest) {
log.info("[执行登录接口]")；
String username = data.get("username")；
String email = data.get("email")；
String phone = data.get("phone")；
String password = data.get("password")；
List resultList = null；
Map<String， String> map = new HashMap<>()；
if(username != null && "".equals(username) == false){
map.put("username"， username)；
resultList = service.select(map， new HashMap<>()).getResultList()；
}
else if(email != null && "".equals(email) == false){
map.put("email"， email)；
resultList = service.select(map， new HashMap<>()).getResultList()；
}
else if(phone != null && "".equals(phone) == false){
map.put("phone"， phone)；
resultList = service.select(map， new HashMap<>()).getResultList()；
}else{
return error(30000， "账号或密码不能为空")；
}
if (resultList == null || password == null) {
return error(30000， "账号或密码不能为空")；
}
//判断是否有这个用户
if (resultList.size()<=0){
return error(30000，"用户不存在")；
}
User byUsername = (User) resultList.get(0)；
Map<String， String> groupMap = new HashMap<>()；
groupMap.put("name"，byUsername.getUserGroup())；
List groupList = userGroupService.select(groupMap， new HashMap<>()).getResultList()；
if (groupList.size()<1){
return error(30000，"用户组不存在")；
}
UserGroup userGroup = (UserGroup) groupList.get(0)；
//查询用户审核状态
if (!StringUtils.isEmpty(userGroup.getSourceTable())){
String sql = "select examine_state from "+ userGroup.getSourceTable() +" WHERE user_id = " + byUsername.getUserId()；
String res = String.valueOf(service.runCountSql(sql).getSingleResult())；
if (res==null){
return error(30000，"用户不存在")；
}
if (!res.equals("已通过")){
return error(30000，"该用户审核未通过")；
}
}
//查询用户状态
if (byUsername.getState()!=1){
return error(30000，"用户非可用状态，不能登录")；
}
String md5password = service.encryption(password)；
if (byUsername.getPassword().equals(md5password)) {
// 存储Token到数据库
AccessToken accessToken = new AccessToken()；
accessToken.setToken(UUID.randomUUID().toString().replaceAll("-"， ""))；
accessToken.setUser_id(byUsername.getUserId())；
tokenService.save(accessToken)；
// 返回用户信息
JSONObject user = JSONObject.parseObject(JSONObject.toJSONString(byUsername))；
user.put("token"， accessToken.getToken())；
JSONObject ret = new JSONObject()；
ret.put("obj"，user)；
return success(ret)；
} else {
return error(30000， "账号或密码不正确")；
}
}
5.2用户管理界面
用户通过注册了方可获得登录使用权限，此时选择注册用户选项，系统就会自动转到用户注册工作面，在注册该部分信息时系统会自动调用add函数，然后在给定的文本框中填写有关该用户的基础信息后选择确认即可完成注册。检索用户信息，在新增用户信息以后，在检索工具栏中填写对应的用户信息，系统就会将该用户有关的所有信息展示出来。
用户管理流程图如下所示。
图5-3 用户管理流程图
用户管理界面如下图所示。
图5-4用户管理界面图
5.3部门管理界面
管理员执行部门管理，并可以操作相关内容，例如添加，查看，编辑和删除。通过单击“添加部门”，可以通过部门添加界面添加详细信息。单击查看字段级别链接以查看有关所选字段级别的信息。然后单击“提交”跳转重返到添加页面。添加成功后的信息会载入到部门查询列表中，管理员可进行编辑以及修改。
部门添加流程图如下所示。
图5-1 部门管理流程图
部门管理如下图所示。
图5-6 部门管理界面图
5.4财务请假管理界面
财务提交请假，可以进行新增、查看、修改以及删除等相应的请假管理操作。当点击"新增请假"的按钮时，在请假添加界面进行详细信息的添加操作。当点击"查看请假"超级链接时，会显示所选的请假的信息，然后点击"返回"再返回到其主页面。
财务请假提交界面如图所示。
图5-7财务请假界面图
财务请假逻辑代码如下所示。
@RequestMapping(value = "/del")
@Transactional
public Map<String， Object> del(HttpServletRequest request) {
service.delete(service.readQuery(request)， service.readConfig(request))；
return success(1)；
}
@Transactional
public void delete(Map<String，String> query，Map<String，String> config){
StringBuffer sql = new StringBuffer("DELETE FROM ").append("`").append(table).append("`").append(" ")；
sql.append(toWhereSql(query， "0".equals(config.get(FindConfig.GROUP_BY))))；
log.info("[{}] - 删除操作：{}"，table，sql)；
Query query1 = runCountSql(sql.toString())；
query1.executeUpdate()；
}
5.5床位信息管理界面
添加床位信息时，输入必填字段后，表现层的LaorenController接受传过来的床位信息参数，再调用LaorenController类的addLaoren方法，经过LaorenService业务层到LaorenMapper持久层的处理，完成对整个添加床位信息的操作。addLaoren方法也和用户管理中的addUser方法类似，同时做添加和修改工作。
修改床位信息时，选择需要修改的床位进行修改，调用LaorenController控制器的editLaoren方法，拿到该床位原本的信息并显示到页面，管理员再对需要修改的床位信息字段进行修改，完成后调用addLaoren方法，调用业务层的updateByKey方法，更新数据库的床位信息表的数据。
床位管理流程图如下所示。
图5-8床位管理流程图
床位信息管理界面如下图所示。
图5-9床位信息管理界面图
5.6护理考勤管理界面
删除护理考勤时，选择需要删除的护理考勤进行删除，把主键的uId传到YihurenyuanController控制器，再调用控制器的deleteYihurenyuan方法，数据经过YihurenyuanService业务层解析和处理，请求YihurenyuanMapper持久层调用deleteByPrimaryKey方法操作数据库将护理考勤数据从数据库中删除。
查找护理考勤时，输入需要查找的员工姓名，调用getData方法获取所有数据并且进行分页，把获取到的所有数据显示到视图上，这时候只需要用脚本方法便能快速查找，不涉及对数据库操作。
护理考勤管理流程图如下所示。
图5-10护理考勤管理流程图
护理考勤管理界面如下图所示。
图5-11 护理考勤管理界面
护理考勤的逻辑代码如下：
@PostMapping("/add")
@Transactional
public Map<String， Object> add(HttpServletRequest request) throws IOException {
service.insert(service.readBody(request.getReader()))；
return success(1)；
}
@Transactional
public Map<String， Object> addMap(Map<String，Object> map){
service.insert(map)；
return success(1)；
}
public Map<String，Object> readBody(BufferedReader reader){
BufferedReader br = null；
StringBuilder sb = new StringBuilder("")；
try{
br = reader；
String str；
while ((str = br.readLine()) != null){
sb.append(str)；
}
br.close()；
String json = sb.toString()；
return JSONObject.parseObject(json， Map.class)；
}catch (IOException e){
e.printStackTrace()；
}finally{
if (null != br){
try{
br.close()；
}catch (IOException e){
e.printStackTrace()；
}
}
}
return null；
}
public void insert(Map<String，Object> body){
StringBuffer sql = new StringBuffer("INSERT INTO ")；
sql.append("`").append(table).append("`").append(" (")；
for (Map.Entry<String，Object> entry:body.entrySet()){
sql.append("`"+humpToLine(entry.getKey())+"`").append("，")；
}
sql.deleteCharAt(sql.length()-1)；
sql.append(") VALUES (")；
for (Map.Entry<String，Object> entry:body.entrySet()){
Object value = entry.getValue()；
if (value instanceof String){
sql.append("'").append(entry.getValue()).append("'").append("，")；
}else {
sql.append(entry.getValue()).append("，")；
}
}
sql.deleteCharAt(sql.length() - 1)；
sql.append(")")；
log.info("[{}] - 插入操作：{}"，table，sql)；
Query query = runCountSql(sql.toString())；
query.executeUpdate()；
}
5.7老人信息管理界面
管理员执行老人信息管理，并可以操作相关内容，例如添加，查看，编辑和删除。通过单击“添加老人信息”，可以通过老人信息添加界面添加详细信息。单击查看字段级别链接以查看有关所选字段级别的信息。然后单击“提交”跳转重返到添加页面。添加成功后的信息会载入到老人信息查询列表中，管理员可进行编辑以及修改。
老人信息添加流程图如下所示。
图5-11 老人信息添加流程图
老人信息管理如下图所示。
图5-13 老人管理界面
6系统测试
系统开发的最后一个步骤就是系统测试，系统测试也是整个系统十分重要的一个环节，测试的好坏关系到产品的发展。用户对软件的质量、性能和可靠性等需求就要通过测试来实现。测试过程要必须遵循严谨性、完善性、规范性的原则，测试的主要目的就是看看在系统运行中，是否会出现bug，然后对出现的bug进行调试，直到程序完美运行。但是软件的测试只能尽可能的减少bug，理论上来说是无法达到消除bug。但是bug越少，系统出错的几率就越低，用户使用起来也更方便、更安全。
近年来，软件包含测试从现在的检验当中来看，系统接近预期目标可能出现的问题，并对这些错误做出相应的修正，假如我们不进行早期的测试错误就会延续下去，最后所做出的成品就会有很大的困难。
我们要在这个测试的过程当中找出错误。测试成软件开发的主要一部分，自从有了程序的设计那天开始，它就成为了重要的组成部分。经过统计来看，软件测试可以占据这个系统45%的工作量，而在软件开发的成本当中，对于测试成本来说它包含了很多的测试工作。每个程序测试时都会出现和遇到错误。在整个程序的开发过程当中，人为去查找错误是非常复杂和困难的，所以我们一般都会找一些测试的工具来进行测试。
6.1系统测试的意义
随着现代信息的快速发展，在社会各大领域中已经都开始应用网络信息技术，在应用网络技术的同时人们也开始把软件的质量问题作为了一个重要焦点来关注，因为一个软件的好与坏它决定着这个系统在市场上的生存，所以我们必须要把软件质量来做好，这样才有一定的生存能力。对于用户来说它们首先选用的都是保证这个系统软件的质量问题，因为一个系统的软件质量决定着用户在后期上成本经济的问题。
6.2 测试方法
黑盒测试又被人们称作为功能测试，通常是在程序的接口来做一些测试的方法，它一般包括对程序的功能和使用的方法来做出一些数据的接受和输出，同时还可以做出正确的输出信息，并保证与外部信息的完整性。
白盒测试通常被人们称作为结构测试，在整个程序的结构和处理当中它是由程序当中的逻辑测试和检验程序来完成一些正确的工作。
具体的功能测试它是包括：系统的适用性、准确性、安全性等功能测试。
6.3测试分析
基于养老院管理系统满足相关信息的管理需求，在设计时借鉴了国内外优秀网站的优点，从界面到系统设计都保证了管理员以及用户能够方便操作。系统的主要特点和优点归纳如下：
（1）本系统用的移置性和针对性都比较高，因为针对性高可以提供更好的服务而移置性可以在多个系统上运行，更给用户带来了极大的方便。
（2）该基于养老院管理系统内容全面，管理方便可以及时的全面的处理各种错误，异常，这样避免了很多因用户的马虎操作而出现的失误，其操作方便，用户界面友好，能够上网的人都可以很好的进行操作。
经过对上述的测试结果分析，所有基本功能齐全，操作简单，系统运行性能良好，系统安全可靠，能促进基于养老院管理系统的发展，发展前景广阔。
结 论
本系统通过对java和Mysql数据库的简介，从硬件和软件两反面说明了基于养老院管理系统的可行性，本文结论及研究成果如下：实现了java与Mysql相结合构建的基于养老院管理系统，网站可以响应式展示。通过本次基于养老院管理系统的研究与实现，我感到学海无涯，学习是没有终点的，而且实践出真知，只有多动手才能尽快掌握它，经验对系统的开发非常重要，经验不足，就难免会有许多考虑不周之处。比如要有美观的界面，更完善的功能，才能吸引更多的用户。
由于在此之前对于java知识没有深入了解，所以从一开始就碰到许多困难，例如一开始的页面显示不规范、数据库连接有问题已经无法实现参数的传递等等，不过通过在网上寻找有关资料以及同学的帮助下最后都得到了解决，在此过程中，我不仅学到了很多知识，也提高了自己解决问题的能力，尤其是学会如何从大量的信息中筛选出所需有用的信息，同时我更加深刻的体会到了，虽然书本上的大部分知识都是有价值，正确的，但实际上每个人编程的思路和对数据处理的方法、思想都是不同的，这就要求我们一定要通过实践才能找到解决问题的方案。在此次毕业设计活动中，我不断的提高了自己，也得到了宝贵的经验，我相信这些对我以后的发展都会有很大帮助。
通过这次基于养老院管理系统的开发，我参考了很多相关系统的例子，取长补短，吸取了其他系统的长处，逐步对该系统进行了完善，但是该系统还是有很多的不足之处，有待以后进一步学习。
实践证明，基于养老院管理系统有着非常好的发展前景，经过测试运行，系统各项功能都十分完善，界面漂亮，使用方便，操作容易，在技术理论上已经成熟。
致 谢
大学的学习生活在这个季节将结束，但是在我的生命这仅仅只是一个逗号，我将面对的旅程的另一个的开始。通过这次毕业设计的整个开发过程，从需求分析到具体功能实现，再到最终测试和维护的理解有了很大的进步，让我对系统开发有了更深刻的认识，对我个人的实践能力和解决问题的能力，都有了很大的帮助。这是这次毕业设计最大的收获。
首先要感谢我的指导老师，他在论文写作上，给予了我各种无私的帮助，治学严谨，严格要求，使我获得了很大的收获。老师深厚的理论知识和丰富的实践经验，都深深的影响到我，在这方面，我谨表示衷心的感谢。
其次，我还要对所有的老师和同学表示感谢，他们在我学习的过程中，都积极的提供了很多帮助，无论是专业知识，还是实践操作技能，也能够让我在论文写作中，遇到的一些难题迎刃而解。
最后，对阅读和评审本论文的各位老师表示衷心的感谢!
参考文献
[1]刘亚茹,张军.Vue.js框架在网站前端开发中的研究[J].电脑编程技巧与维护,2022(01):18-19+39.DOI:10.16184/j.cnki.comprg.2022.01.009.
[2]李弟文.应用Vue的百倍课堂Web端系统设计与实现[J].福建电脑,2021,37(12):75-81.DOI:10.16707/j.cnki.fjpc.2021.12.017.
[3]裴之蕈,高艳霞.基于Vue和Node.js的手语教学Web平台的设计与实现[J].电脑与信息技术,2021,29(06):33-36+86.DOI:10.19414/j.cnki.1005-1228.2021.06.010.
[4]单树倩,任佳勋.基于SpringBoot和Vue框架的数据库原理网站设计与实现[J].电脑知识与技术,2021,17(30):40-41+50.DOI:10.14004/j.cnki.ckt.2021.2868.
[5]苏文强,刘紫阳,苗玉恒.基于SpringBoot的缺陷管理系统设计与实现[J].大众科技,2021,23(10):4-6+10.
[6]王萍.SpringBoot项目中EhCache缓存技术的实现[J].电脑知识与技术,2021,17(29):79-81.DOI:10.14004/j.cnki.ckt.2021.2812.
[7]Xinwen Zhang,Siyuan Wen,Rui Wang. Implementation of Vehicle Management System Based on Spring Boot and VUE[C]//第33届中国控制与决策会议论文集（9）.,2021:519-523.DOI:10.26914/c.cnkihy.2021.028243.
[8]Pra Denis R.. Emmanuel Carrère: le point de vue de l’adversaire éd. par Christophe Reig, et al (review)[J]. The French Review,2021,91(1):
[9]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):
[10] Shen Mengqi. Nursing home management system based on Internet of Things technology [J]. Computer Products and Circulation, 2019(08):122.
[11] Zhang Yuan, Lu Jianhua, Yu Zaihan. Nursing home system design based on Internet of Things technology [J]. Science and Technology Wind, 2019(05):87-88.DOI:10.19392/j.cnki.1671-7341.201905076.
[12] Wu Yuan. Research on smart elderly care system based on Internet of Things [D]. Lanzhou University, 2018.
To receive the project source code for free, please follow and like + private message