Table of contents
1.1 Project Background of System Development
1.2 Purpose of system development
1.3 Paper Structure and Chapter Arrangement
2 Case Management System Analysis of Private Dental Clinics
2.2.2 Data modification process _
3 Overall Design of Case Management in Private Dental Clinic
3.1 System architecture design
3.2 System function module design
3.2.1 Overall functional module design
3.2.3 Comment management module design
3.2.4 Department information management module design
3.2.5 Registration information management module design
3.3.1 Database conceptual structure design
3.3.2 Database logical structure design
4 Detailed design and implementation of case management in private dental clinics
4.1.2 User registration interface
4.1.4 Bulletin board interface
4.1.5 Dental information interface
4.1.6 Department details interface
4.3 Administrator function module
4.3.1 Site management interface
4.3.2 User Management Interface
4.3.3 Dental information interface
4.3.4 More management interfaces
In the information society, there is a need for targeted information acquisition channels, but the expansion of channels is basically the direction that people are striving for. Due to the deviation in their perspective, people can often obtain different types of information, which is also the most difficult technology to overcome. topic. Aiming at problems such as case management in private dental clinics, conduct research and analysis on case management in private dental clinics, and then develop and design case management in private dental clinics to solve the problems.
The main functional modules of private dental clinic case management include user management, department center, appointment information, registration information, charging information, case information, message information, drug management, adding records, sales records, and adopt an object-oriented development model for software development. The development and hardware installation can well meet the needs of actual use, and the corresponding software installation and program coding work has been improved. MySQL is used as the main storage unit for background data, and SSM framework, JAVA technology, and Ajax technology are used for business. The coding and development of the system have realized all the functions of the system. This report first analyzes the background, function and significance of the research, laying the foundation for the rationality of the research work. Analyzed the needs and technical problems of case management in private dental clinics, proved the necessity and technical feasibility of the system, and then gave a basic introduction to the technical software and design ideas that need to be used in the design system, and finally realized private dentistry Clinic case management and deployment runs use it.
Key words : SSM technology; MYSQL; private dental clinic case management
Abstract
In the information society, there is a need for targeted information access, but the expansion of access is basically the direction of people's efforts. Due to the deviation of the perspective, people can often obtain different types of information, which is also the most difficult subject for technology to overcome. Aiming at the problems of case management in private dental clinic, this paper studies and analyzes the case management in private dental clinic, and then develops and designs the case management in private dental clinic to solve the problems.
The main functional modules of case management in private dental clinic include user management, Department Center, reservation information, registration information, charging information, case information, message information, drug management, adding records and selling records. The object-oriented development mode is adopted for software development and hardware erection, which can well meet the needs of actual use and improve the corresponding software erection and program coding, MySQL is used as the main storage unit of background data, and SSM framework, Java technology and Ajax technology are used to code and develop the business system, which realizes all the functions of the system. This report first analyzes the background, function and significance of the research, which lays a foundation for the rationality of the research work. This paper analyzes the various needs and technical problems of case management in private dental clinic, proves the necessity and technical feasibility of the system, and then makes a basic introduction to the technical software and design idea needed to design the system. Finally, it realizes the case management and deployment of private dental clinic.
Keywords:SSM technology; MYSQL； Case management in private dental clinics
1 Introduction
HOSPITAL INFORMATION SYSTEM (HOSPITAL INFORMATION SYSTEM), referred to as HIS, is an important basic project for the modernization of private dental clinics, and a necessary means to improve the case management level, medical level, business operation efficiency and service quality of private dental clinics. Refers to the computer application software that uses computer and network communication equipment to collect, store, process, extract and communicate data on patient medical information, financial accounting analysis information, and appointment information in private dental clinics to meet the information use needs of all authorized users system.
1.1 Project background of system development
With the rapid development of the computer industry, electronic computers have been widely used in information management, word processing, aided design, aided teaching and people's daily life. The dental clinic management system is mainly aimed at the management of a series of related work in the outpatient management of each hospital. The establishment of this system makes the management of the dental clinic more standardized and systematic, and the query methods are more convenient. At the same time, the system adopts the object-oriented development method, which further solves the problems of low software reuse and difficult maintenance of software products in the structured paradigm.
In recent years, with the gradual increase in the number of patients visiting a doctor, manual writing data has been unable to handle such a huge amount of data. In order to better adapt to the efficiency of the information age, a system that uses computers to realize the work of the dental clinic management system must be born. Based on this, the designed dental clinic management system is used to manage the clinic so that the entire management process can be completed efficiently and accurately in the shortest possible time.
Based on the above understanding, collect relevant information and data, consult relevant literature and technical parameters, conduct research on user needs, and find that the manual recording method adopted recently has a wide range of objects in management, data storage is not easy, and it is not easy to archive, thousands. Tens of thousands of information and piles of documents are a burden for managers and require a lot of documentation. However, some clinic management system softwares that have been designed toward the process have a low degree of software reuse, and the software products are not easy to maintain. In view of the above reasons, the management of dental clinics urgently needs an object-oriented design software to manage data.
The application of computer technology in modern management makes computer an important tool for leaders and managers to apply modern technology. Computer-assisted outpatient management activities can greatly enhance the ability of managers to collect and process information, which is conducive to timely decision-making by managers. The computer system can process and save the original data and materials according to the changes in the management process. When the management personnel need information and materials to solve specific problems, they can search and query at any time to understand the dynamic situation of the entire dental clinic management system and carry out dynamic Management, so as to effectively handle the management of dental clinics, realize the automation of dental clinic management, and improve efficiency.
1.2 Purpose of system development
The development purpose of the dental clinic management system is to change the dental clinic management system mode from manual records to information management, from process-oriented development software to object-oriented development software, to provide convenience for outpatient management personnel and software maintenance staff . Conduct research on the actual situation of users, conduct detailed demand analysis, improve the existing management model, and develop a new object-oriented management system, from which we can understand the ideas of system development and master the process and methods of system development. With the continuous improvement of outpatient information system, hospital management will increasingly rely on information management. Therefore, the system development will focus on the actual situation of dental clinic work, so that it can quickly adapt to the needs of various dental clinics.
The practical significance of the realization of the dental clinic management system: reduce the number of staff in the management clinic; the management staff can browse and view at any time, and it is more intuitive; it has changed the way of manual salary recording in the past, and the computer input is faster and more convenient; it has realized the computerization of the outpatient management system. change.
With the vigorous development of digital construction of private dental clinic cases, the concept of digitized private dental clinic cases has been widely accepted by large private dental clinic cases. The main problem currently facing is how to build digital private dental clinic cases. Therefore, at present, the construction of digital private dental clinic cases in my country must focus on medical digitalization, that is, to focus on the development of digital management and comprehensive utilization of various information related to medical activities in private dental clinic cases, so as to realize the digitization of diagnosis and treatment work and medical procedures. The automation of the system and the openness of the system are guaranteed, laying the foundation for future expansion to regional medical care. Correspondingly, as the medical information system is the system foundation of digital private dental clinic case construction, its research focus will also turn to various medical information systems and their integration research for pure medical activities. The overall planning of digital private dental clinic cases focusing on medical digitalization is realized through the organic integration of various medical information systems. It can be said that the new generation of medical information system will play a decisive role in the construction of "digital private dental clinic cases".
1.3 Paper Structure and Chapter Arrangement
The thesis will be arranged in layers, except for the abstract acknowledgments and references, the main text will also analyze the requirements of the website, explain the general design and implemented functions, and finally list some commissioning records. The main structure of the thesis is as follows:
Chapter 1: Introduction. The first chapter mainly introduces the background of the subject research, the status quo of system development and the research content and main work of this paper.
Chapter Two: System Requirements Analysis. The second chapter mainly conducts demand analysis from the aspects of system users and functions.
Chapter Three: System Design. The third chapter mainly carries on the function design to the system frame, the system function module, the database.
Chapter Four: System Realization. The fourth chapter mainly introduces the construction of the system framework and the realization of the system interface.
Chapter Five: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions
2 Analysis of Case Management in Private Dental Clinics
System analysis is a prerequisite for developing a project. Through system analysis, the basic needs of the main users of the system can be well understood, and this is also the reason for the development of the project. Further, feasibility analysis is carried out on system development, usually including technical feasibility, economic feasibility, etc. Feasibility analysis is also an analysis from the overall perspective of the project. Then it is to analyze the specific needs of the project, and the means of analysis are generally realized through the user's use case diagram. The following is a detailed introduction.
2.1 Feasibility analysis
Most of the tools used in the project are currently popular open source and free, so in the early stage of development, the funds used for the project will be greatly reduced, and the development of the software will not be affected by the funds during the project start-up period, so It is still economically feasible. Try to use the least cost to meet the needs of users. Save funds for labor costs and equipment costs. It will go further and further on the road of paperless and high efficiency.
So there is no question of economic viability.
(2) Operation feasibility:
The design of this project refers to several development cases of websites under this mode, analyzes their operation interface, combines many cases together, and highlights the people-oriented and simplified operation, so people with basic computer knowledge can operate this project.
Therefore, there is no problem with operability.
(3) Technical feasibility:
Technical feasibility refers to the feasibility of building a framework, and the acceptability of system technology upgrades when better technologies emerge, and the ratio of development time to cost.
The existing Java technology can cater to the construction of all e-commerce systems. When developing the case management of this private dental clinic, I used Java+MYSQL to run the overall program.
In summary, there is no problem with the technical feasibility.
(4) Legal feasibility:
From the perspective of developers, Java and MYSQL are open source and free online, and there will be no legal disputes in terms of intellectual property rights.
From the perspective of user use, as long as no contraband is sold on the system, a treaty agreement is made on the system, and illegal payments are eliminated.
In summary, there is no question of legal feasibility.
The business process is to use some specific symbols and lines to demonstrate the user's process of using the system. When performing system analysis, the business process can help developers better understand the business, find errors, and improve the system.
After the user successfully logs in to the system , the operation of adding data can be realized. The number of adding data is specific and generated by the system, and the user cannot fill it in at will. Except for the number, the user can fill in other additional information by himself, and the filled information is verified by the system and verified to be legal. Passing shows that the data addition is successful. On the contrary, the addition is not successful. Figure 2-1 shows the process of adding data.
Figure 2-1 Flowchart of adding data
2.2.2 Data modification process
The process of data modification is similar to the process of data addition described above, as shown in Figure 2-2 .
Figure 2-2 Data modification flow chart
If there are some useless data in the system , the relevant management personnel can also delete these data. Figure 2-3 is the flow chart of data deletion.
Figure 2-3 Data deletion flow chart
2.3 System function analysis
According to the role of private dental clinic case management, I divided it into three parts: general user management module, doctor user management module and administrator management module.
User management module:
(1) User registration and login: the user registers as a member and logs in to the private dental clinic case management; the user adds, deletes, modifies and checks personal information, such as personal information and password modification.
(3) Bulletin board: On the navigation bar of the homepage, we will see the menu of " Bulletin News ". After we click to enter, we will see the bulletin information released by all administrators in the background;
(4) Dental information : On the navigation bar of the homepage, we will see the menu of " Dental Information ". Like, if you want to find this information faster next time, you can also bookmark and comment;
(5) Department Center : On the navigation bar of the home page, we will see the menu of " Department Information ". After we click to enter, we will see the department information released by all administrators in the background . We choose to make an appointment to know about the department For information , you can like + bookmark + register + make an appointment + comment ;
(6) My Favorites: Under "My", you can view and manage the "My Favorites" information, you can view the favorites, and you can also delete the favorite information;
(6) My account: When the user clicks the "My" button in the upper right corner, a submenu will appear, click "My Account" to set the personal information and the password to log in to the system;
(7) Personal Center: When the user clicks the "My" button in the upper right corner, he will enter the corresponding background for information management;
Administrator management module:
(1) Login: The account of the administrator is directly set and generated in the data table, and no registration is required;
(2) Site management: When you click on the "Site Management" menu, two sub-menus will appear, carousel map + bulletin board, and you can add, delete, modify and check these two modules;
(3) User management: When you click on the "User Management" menu, three sub-menus will appear: administrator + doctor user + ordinary user , and you can add, delete, modify and query these three
(4) Content management: When you click on the "Content Management" menu, two sub-menus will appear: Dental Information + Dental Information Classification , which can manage the dental information submitted by the user at the front desk , and at the same time display the dental information at the front desk Add, delete, modify and query classified information;
(5) More management: When you click the "More" menu, there will be nine department centers + appointment information + registration information + charging information + case information + message information + drug management + add records + sales records There are two sub-menus, which can add, delete, modify and check the nine modules;
(6) Mall management: Comprehensive management of all departments, department classifications and order information submitted by users in the case management of private dental clinics.
2.3.2 Non-functional analysis
Non-functional requirements for case management in private dental clinics, such as the security, reliability, performance, and scalability of case management in private dental clinics. Specifically, it can be expressed in the following table 3-1:
Table 3-1 Non-functional requirements table for case management in private dental clinics
| safety |
It mainly refers to the installation of the case management database in private dental clinics. The use of the database and the setting of passwords must comply with the regulations. |
| reliability |
Reliability means that the case management of private dental clinics can be operated according to the user's instructions. After testing, the reliability is more than 90%. |
| performance |
Performance is a necessary condition for case management of private dental clinics to occupy the market, so the best performance is the best. |
| scalability |
For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system. |
| ease of use |
Users only need to follow the content displayed on the page of private dental clinic case management. |
| maintainability |
The maintainability of case management development in private dental clinics is very important, after testing, there is no problem with maintainability |
2.4 System use case analysis
Through the analysis of 2.3 functions, the use case diagram of case management in this private dental clinic is obtained:
Figure 2-3 shows an example of a user role.
Figure 2-3 Use Case Diagram of Case Management User Role in Private Dental Clinic
The administrator on the web background management maintains all data information in the case management of the entire private dental clinic. An example of a doctor user role is shown in Figure 2-4.
Figure 2-4 Use Case Diagram of Doctor User Role in Case Management in Private Dental Clinic
The administrator on the web background management maintains all data information in the case management of the entire private dental clinic. Figure 2-5 shows an example of an administrator role.
figure 2-5 Private Dental Practice Case Management Administrator Role Use Case Diagram
This chapter mainly determines the functions to be realized in the case management of the entire private dental clinic through the feasibility analysis, process analysis, functional requirement analysis, and system use case analysis of the private dental clinic case management. It also provides standards for code implementation and testing for case management in private dental practices.
3 Overall Design of Case Management in Private Dental Clinic
This chapter mainly discusses the functional module design and database system design of private dental clinic case management.
3.1 System architecture design
The case management of this private dental clinic is divided into three layers from the architecture: presentation layer (UI), business logic layer (BLL) and data layer (DL).
Figure 3-1 Architecture Design Diagram of Case Management System in Private Dental Clinic
Presentation layer (UI): Also known as UI layer, it mainly completes the UI interaction function of case management in this private dental clinic. A good UI can improve the user experience of users and enhance the comfort of users when using case management in this private dental clinic . The UI interface design should also adapt to different versions of private dental clinic case management and different size resolutions to achieve good compatibility. The requirements for UI interaction functions are reasonable, and users must obtain consistent interaction results when performing interactive operations, which requires a good connection between the presentation layer and the business logic layer.
Business Logic Layer (BLL): It mainly completes the data processing function of case management in this private dental clinic. The data transmitted by the user from the presentation layer is processed and delivered to the data layer through the business logic layer, and the data read by the system from the data layer is processed and delivered to the presentation layer through the business logic layer.
Data layer (DL): Since the case management data of this private dental clinic is placed in the mysql database on the server side, the part that belongs to the service layer can be directly integrated into the business logic layer, so there is only the database in the data layer, which mainly completes Data storage and management functions for case management in this private dental practice.
3.2 System function module design
3.2.1 Overall functional module design
In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in the case management of this private dental clinic were analyzed according to the requirements. Then the next step is to start designing the structure, main functions and database of the case management of this private dental clinic. The case management of private dental clinics is obtained based on the requirements analysis in the previous chapters, and its overall design module diagram is shown in Figure 3-2.
Figure 3-2 Functional module diagram of case management in a private dental clinic
3.2.2 User module design
The background manager can add, delete, modify and check the users registered in the front desk. The structure diagram of the user module is as follows:
Figure 3-3 Structure Diagram of Member User Module
3.2.3 Comment management module design
Case management in private dental clinics is an open platform for communication. Member users can communicate on the platform to increase the interaction between users. But at the same time, in order to better regulate the content of the message and give the administrator the function of deleting inappropriate comments, it is necessary to design a message management module. The specific structure diagram is as follows:
Figure 3-4 Structure diagram of message module
3.2.4 Department information management module design
The case management of private dental clinics needs to store a lot of department information, and its module function structure, the specific structure diagram is as follows:
Figure 3-5 Department module structure diagram
3.2.5 Registration information management module design
One of the most important functions of case management in a private dental clinic is to make an appointment . Its module function structure, the specific structure diagram is as follows:
Figure 3-5 Structural Diagram of Registration Information Module
Database design generally includes three major processes: requirements analysis, conceptual model design, and database table establishment. Requirements analysis has been explained in the previous chapters, and conceptual model design has two parts: conceptual model and logical structure design.
3.3.1 Conceptual structure design of database
The following is the ER entity relationship diagram of the main database tables in the case management of the entire private dental clinic.
Figure 3-6 General ER relationship diagram of private dental clinic case management
According to the general ER relationship diagram of the database for case management in private dental clinics, it can be concluded that case management in private dental clinics requires many ER diagrams. Here are some main database ER model diagrams.
Figure 3-7 Doctor user ER relationship diagram
Figure 3-8 ER relationship diagram of appointment information
Figure 3-9 ER relationship diagram of case information
Figure 3-10 Message ER relationship diagram
3.3.2 Database logical structure design
From the total ER relationship diagram in the case management of private dental clinics in the previous section, it can be concluded that a lot of data tables need to be created. Here I mainly list several major database table structure designs.
sales_record table:
| type |
length |
not null |
primary key |
note |
|
| sales_record_id |
int |
11 |
yes |
yes |
Sales Record ID |
| drug_name |
varchar |
64 |
no |
no |
Drug Name |
| drug_type |
varchar |
64 |
no |
no |
drug type |
| usage_and_dosage |
varchar |
64 |
no |
no |
Dosage |
| sold_doctor |
int |
11 |
no |
no |
sell doctor |
| date_sold |
date |
0 |
no |
no |
date of sale |
| quantity_sold_ |
int |
11 |
no |
no |
Quantity sold |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
update time |
| reservation_information表： |
|||||
| name |
type |
length |
not null |
primary key |
note |
| reservation_information_id |
int |
11 |
yes |
yes |
Reservation Information ID |
| department_name |
varchar |
64 |
no |
no |
Department name |
| department_type |
varchar |
64 |
no |
no |
Department type |
| department_doctor |
int |
11 |
no |
no |
Department doctor |
| on_duty_time |
varchar |
64 |
no |
no |
Working hours |
| patient_user |
int |
11 |
no |
no |
patient user |
| user_name |
varchar |
64 |
no |
no |
username |
| user_gender |
varchar |
64 |
no |
no |
user gender |
| user_age |
varchar |
64 |
no |
no |
user age |
| user_address |
varchar |
64 |
no |
no |
user address |
| time_of_appointment |
datetime |
0 |
no |
no |
Appointment |
| number_of_appointments |
varchar |
64 |
no |
no |
Number of reservations |
| user_profile |
text |
0 |
no |
no |
Disease profile |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
update time |
| registration_information表： |
|||||
| name |
type |
length |
not null |
primary key |
note |
| registration_information_id |
int |
11 |
yes |
yes |
Registration Information ID |
| department_name |
varchar |
64 |
no |
no |
Department name |
| department_type |
varchar |
64 |
no |
no |
Department type |
| department_doctor |
int |
11 |
no |
no |
Department doctor |
| on_duty_time |
varchar |
64 |
no |
no |
Working hours |
| patient_user |
int |
11 |
no |
no |
patient user |
| user_name |
varchar |
64 |
no |
no |
username |
| user_gender |
varchar |
64 |
no |
no |
user gender |
| user_age |
varchar |
64 |
no |
no |
user age |
| user_address |
varchar |
64 |
no |
no |
user address |
| registration_date |
date |
0 |
no |
no |
registration date |
| number_of_registered_persons |
varchar |
64 |
no |
no |
Registration number |
| user_profile |
text |
0 |
no |
no |
Disease profile |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
update time |
| ordinary_users table: |
|||||
| name |
type |
length |
not null |
primary key |
note |
| ordinary_users_id |
int |
11 |
yes |
yes |
common user ID |
| user_number |
varchar |
64 |
yes |
no |
user ID |
| user_name |
varchar |
64 |
no |
no |
username |
| user_gender |
varchar |
64 |
no |
no |
user gender |
| user_age |
varchar |
64 |
no |
no |
user age |
| examine_state |
varchar |
16 |
yes |
no |
Approval Status |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| user_id |
int |
11 |
yes |
no |
User ID |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
update time |
| message_information表： |
|||||
| name |
type |
length |
not null |
primary key |
note |
| message_information_id |
int |
11 |
yes |
yes |
Message ID |
| department_name |
varchar |
64 |
no |
no |
Department name |
| department_type |
varchar |
64 |
no |
no |
Department type |
| department_doctor |
int |
11 |
no |
no |
Department doctor |
| message_user |
int |
11 |
no |
no |
message user |
| message_time |
datetime |
0 |
no |
no |
Message Time |
| message_content |
text |
0 |
no |
no |
Message content |
| recommend |
int |
11 |
yes |
no |
Intelligent Recommendation |
| create_time |
datetime |
0 |
yes |
no |
creation time |
| update_time |
timestamp |
0 |
yes |
no |
update time |
| medical_record_information表： |
|||||
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| medical_record_information_id |
int |
11 |
是 |
是 |
病历信息ID |
| department_name |
varchar |
64 |
否 |
否 |
科室名称 |
| department_type |
varchar |
64 |
否 |
否 |
科室类型 |
| department_doctor |
int |
11 |
否 |
否 |
科室医生 |
| patient_user |
int |
11 |
否 |
否 |
患者用户 |
| user_name |
varchar |
64 |
否 |
否 |
用户姓名 |
| user_gender |
varchar |
64 |
否 |
否 |
用户性别 |
| user_age |
varchar |
64 |
否 |
否 |
用户年龄 |
| add_time |
date |
0 |
否 |
否 |
添加时间 |
| medical_records |
text |
0 |
否 |
否 |
就诊病历 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
| doctor_user表： |
|||||
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| doctor_user_id |
int |
11 |
是 |
是 |
医生用户ID |
| doctor_job_number |
varchar |
64 |
否 |
否 |
医生工号 |
| name_of_doctor |
varchar |
64 |
否 |
否 |
医生姓名 |
| doctor_gender |
varchar |
64 |
否 |
否 |
医生性别 |
| doctor_age |
varchar |
64 |
否 |
否 |
医生年龄 |
| length_of_medical_service |
varchar |
64 |
否 |
否 |
从医时长 |
| doctor_certificate |
varchar |
255 |
否 |
否 |
医生证件 |
| examine_state |
varchar |
16 |
是 |
否 |
审核状态 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| user_id |
int |
11 |
是 |
否 |
用户ID |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
| department_center表： |
|||||
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| department_center_id |
int |
11 |
是 |
是 |
科室中心ID |
| department_name |
varchar |
64 |
是 |
否 |
科室名称 |
| department_type |
varchar |
64 |
否 |
否 |
科室类型 |
| department_doctor |
int |
11 |
否 |
否 |
科室医生 |
| on_duty_time |
varchar |
64 |
否 |
否 |
在岗时间 |
| number_of_reservations |
int |
11 |
否 |
否 |
可就诊数 |
| doctor_picture |
varchar |
255 |
否 |
否 |
医生图片 |
| doctor_profile |
longtext |
0 |
否 |
否 |
医生简介 |
| hits |
int |
11 |
是 |
否 |
点击数 |
| praise_len |
int |
11 |
是 |
否 |
点赞数 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
| charging_information表： |
|||||
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| charging_information_id |
int |
11 |
是 |
是 |
收费信息ID |
| department_doctor |
int |
11 |
否 |
否 |
科室医生 |
| patient_user |
int |
11 |
否 |
否 |
患者用户 |
| charge |
int |
11 |
否 |
否 |
收取费用 |
| charge_date |
date |
0 |
否 |
否 |
收费日期 |
| charging_content |
text |
0 |
否 |
否 |
收费内容 |
| pay_state |
varchar |
16 |
是 |
否 |
支付状态 |
| pay_type |
varchar |
16 |
否 |
否 |
支付类型 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
| drug_administration表： |
|||||
| 名称 |
类型 |
长度 |
不是null |
主键 |
注释 |
| drug_administration_id |
int |
11 |
是 |
是 |
药品管理ID |
| drug_name |
varchar |
64 |
是 |
否 |
药品名称 |
| drug_type |
varchar |
64 |
否 |
否 |
药品类型 |
| quantity_of_drugs |
int |
11 |
否 |
否 |
药品数量 |
| usage_and_dosage |
varchar |
64 |
否 |
否 |
用法用量 |
| drug_picture |
varchar |
255 |
否 |
否 |
药品图片 |
| drug_details |
text |
0 |
否 |
否 |
药品详情 |
| recommend |
int |
11 |
是 |
否 |
智能推荐 |
| create_time |
datetime |
0 |
是 |
否 |
创建时间 |
| update_time |
timestamp |
0 |
是 |
否 |
更新时间 |
3.4本章小结
整个私人牙科诊所病例管理的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4 私人牙科诊所病例管理详细设计与实现
私人牙科诊所病例管理的详细设计与实现主要是根据前面的私人牙科诊所病例管理的需求分析和私人牙科诊所病例管理的总体设计来设计页面并实现业务逻辑。主要从私人牙科诊所病例管理界面实现、业务逻辑实现这两部分进行介绍。
4.1用户功能模块
4.1.1 前台首页界面
当进入私人牙科诊所病例管理的时候，首先映入眼帘的是系统的导航栏，下面是轮播图以及系统内容，其主界面展示如下图4-1所示。
图4-1 前台首页界面图
4.1.2 用户注册界面
不是私人牙科诊所病例管理中正式会员的是可以在线进行注册的，如果你没有本私人牙科诊所病例管理的账号的话，添加“注册”，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号等后再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可会员注册成功。其用用户注册界面展示如下图4-2所示。
图4-2 前台用户注册界面图
注册逻辑关键代码如下所示。
* 注册
* @return
*/
@PostMapping("register")
public Map<String, Object> signUp(HttpServletRequest request) throws IOException {
// 查询用户
Map<String, String> query = new HashMap<>();
Map<String,Object> map = service.readBody(request.getReader());
query.put("username",String.valueOf(map.get("username")));
List list = service.selectBaseList(service.select(query, new HashMap<>()));
if (list.size()>0){
return error(30000, "用户已存在");
}
map.put("password",service.encryption(String.valueOf(map.get("password"))));
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){
E entity = JSON.parseObject(JSON.toJSONString(body),eClass);
baseMapper.insert(entity);
log.info("[{}] - 插入操作：{}",entity);
}
4.1.3 用户登录界面
私人牙科诊所病例管理中的前台上注册后的会员是可以通过自己的账户名和密码进行登录的，当会员输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到私人牙科诊所病例管理的首页中；否则将会提示相应错误信息，用户登录界面如下图4-3所示。
图4-3用户登录界面图
登录系统主要代码如下。
* 登录
* @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;
QueryWrapper wrapper = new QueryWrapper<User>();
Map<String, String> map = new HashMap<>();
if(username != null && "".equals(username) == false){
map.put("username", username);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(email != null && "".equals(email) == false){
map.put("email", email);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(phone != null && "".equals(phone) == false){
map.put("phone", phone);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}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.selectBaseList(userGroupService.select(groupMap, new HashMap<>()));
if (groupList.size()<1){
return error(30000,"用户组不存在");
}
UserGroup userGroup = (UserGroup) groupList.get(0);
//查询用户审核状态
if (!StringUtils.isEmpty(userGroup.getSourceTable())){
String res = service.selectExamineState(userGroup.getSourceTable(),byUsername.getUserId());
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, "账号或密码不正确");
}
}
public String select(Map<String,String> query,Map<String,String> config){
StringBuffer sql = new StringBuffer("select ");
sql.append(config.get(FindConfig.FIELD) == null || "".equals(config.get(FindConfig.FIELD)) ? "*" : config.get(FindConfig.FIELD)).append(" ");
sql.append("from ").append("`").append(table).append("`").append(toWhereSql(query, "0".equals(config.get(FindConfig.LIKE))));
if (config.get(FindConfig.GROUP_BY) != null && !"".equals(config.get(FindConfig.GROUP_BY))){
sql.append("group by ").append(config.get(FindConfig.GROUP_BY)).append(" ");
}
if (config.get(FindConfig.ORDER_BY) != null && !"".equals(config.get(FindConfig.ORDER_BY))){
sql.append("order by ").append(config.get(FindConfig.ORDER_BY)).append(" ");
}
if (config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE))){
int page = config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE)) ? Integer.parseInt(config.get(FindConfig.PAGE)) : 1;
int limit = config.get(FindConfig.SIZE) != null && !"".equals(config.get(FindConfig.SIZE)) ? Integer.parseInt(config.get(FindConfig.SIZE)) : 10;
sql.append(" limit ").append( (page-1)*limit ).append(" , ").append(limit);
}
log.info("[{}] - 查询操作，sql: {}",table,sql);
return sql.toString();
}
public List selectBaseList(String select) {
List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);
List<E> list = new ArrayList<>();
for (Map<String,Object> map:mapList) {
list.add(JSON.parseObject(JSON.toJSONString(map),eClass));
}
return list;
}
4.1.4公告栏界面
当点击导航栏上的“公告栏”的时候，就会进入对应的界面查看公告信息，公告栏界面如下图4-5所示。
图4-4公告栏界面图
4.1.5 牙科资讯界面
用户在点击导航栏上面的牙科资讯后，就可以搜索查看牙科资讯信息，用户根据自己的喜好可以进行查询、评论，牙科资讯界面如下图4-5所示。
图4-5牙科资讯界面图
4.1.6 科室详情界面
当访客点击了任意科室后将会进入该科室的详情界面，可以了解到该科室的科室名称、科室类型、科室医生、在岗时间、可就诊数等，同时可以对该科室进行留言购+收藏+点赞+挂号+预约+评论，科室详情展示页面如图4-6所示。
图4-6 科室详情界面图
4.2管理员功能模块
4.2.1 站点管理界面
私人牙科诊所病例管理中的管理人员在“站点管理”这一菜单中是可以对前台显示的轮播图以及公告栏进行管控。界面如下图4-7所示。
图4-7站点管理界面图
站点管理关键代码如下所示。
@RequestMapping(value = "/del")
@Transactional
public Map<String, Object> del(HttpServletRequest request) {
service.delete(service.readQuery(request), service.readConfig(request));
return success(1);
}
4.2.2 用户管理界面
私人牙科诊所病例管理中的管理人员是可以对前台注册的用户、医生用户进行管理的，也可以对管理员进行管控。界面如下图4-8所示。
图4-8用户管理界面图
用户管理关键代码如下所示。
public List selectBaseList(String select) {
List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);
List<E> list = new ArrayList<>();
for (Map<String,Object> map:mapList) {
list.add(JSON.parseObject(JSON.toJSONString(map),eClass));
}
return list;
}
4.2.3 牙科资讯界面
私人牙科诊所病例管理中管理人员是可以对私人牙科诊所病例管理内的牙科资讯信息进行维护和管理的。牙科资讯界面如下图4-9所示。
图4-9牙科资讯界面图
私人牙科诊所病例管理中的管理人员在“更多管理”这一菜单下是可以对私人牙科诊所病例管理内的科室信息、挂号信息、预约信息、留言信息、药品管理、收费信息、售出记录、添加记录、病例信息进行管控的，其管理界面如下图4-10所示。
图4-11更多管理界面图
5系统测试
系统开发到了最后一个阶段那就是系统测试，系统测试对软件的开发其实是非常有必要的。因为没什么系统一经开发出来就可能会尽善尽美，再厉害的系统开发工程师也会在系统开发的时候出现纰漏，系统测试能够较好的改正一些bug，为后期系统的维护性提供很好的支持。通过系统测试，开发人员也可以建立自己对系统的信心，为后期的系统版本的跟新提供支持。
系统测试包括：用户登录功能测试、科室展示功能测试、科室添加、科室搜索、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：
表5-1 用户登录功能测试表
| 用例名称 |
用户登录系统 |
| 目的 |
测试用户通过正确的用户名和密码可否登录功能 |
| 前提 |
未登录的情况下 |
| 测试流程 |
1) 进入登录页面 2) 输入正确的用户名和密码 |
| 预期结果 |
用户名和密码正确的时候，跳转到登录成功界面，反之则显示错误信息，提示重新输入 |
| 实际结果 |
实际结果与预期结果一致 |
科室查看功能测试：
表5-2 科室查看功能测试表
| 用例名称 |
科室查看 |
| 目的 |
测试科室查看功能 |
| 前提 |
用户登录 |
| 测试流程 |
点击科室列表 |
| 预期结果 |
可以查看到所有科室信息 |
| 实际结果 |
实际结果与预期结果一致 |
管理员添加科室界面测试：
表5-3 管理员添加科室界面测试表
| 用例名称 |
科室发布测试用例 |
| 目的 |
测试科室发布功能 |
| 前提 |
员工用户正常登录情况下 |
| 测试流程 |
1）员工点击科室信息管理就，然后点击添加后并填写信息。 2）点击进行提交。 |
| 预期结果 |
提交以后，页面首页会显示新的科室信息 |
| 实际结果 |
实际结果与预期结果一致 |
科室搜索功能测试：
表5-4科室搜索功能测试表
| 用例名称 |
科室搜索测试 |
| 目的 |
测试科室搜索功能 |
| 前提 |
无 |
| 测试流程 |
1）在搜索框填入搜索关键字。 2）点击搜索按钮。 |
| 预期结果 |
页面显示包含有搜索关键字的科室 |
| 实际结果 |
实际结果与预期结果一致 |
密码修改功能测试：
表5-5 密码修改功能测试表
| 用例名称 |
密码修改测试用例 |
| 目的 |
测试管理员密码修改功能 |
| 前提 |
管理员用户正常登录情况下 |
| 测试流程 |
1）管理员密码修改并完成填写。 2）点击进行提交。 |
| 预期结果 |
使用新的密码可以登录 |
| 实际结果 |
实际结果与预期结果一致 |
通过编写私人牙科诊所病例管理的测试用例，已经检测完毕用户登录模块、科室查看模块、科室添加模块、科室搜索模块、密码修改功能测试，通过这5大模块为私人牙科诊所病例管理的后期推广运营提供了强力的技术支撑。
至此，私人牙科诊所病例管理已经结束，在开发前做了许多的准备，在本系统的设计和开发过程中阅览和学习了许多文献资料，从中我也收获了很多宝贵的方法和设计思路，对系统的开发也起到了很重要的作用，系统的开发技术选用的都是自己比较熟悉的，比如Web、Java技术、MYSQL，这些技术都是在以前的学习中学到了，其中许多的设计思路和方法都是在以前不断地学习中摸索出来的经验，其实对于我们来说工作量还是比较大的，但是正是由于之前的积累与准备，才能顺利的完成这个项目，由此看来，积累经验跟做好准备是十分重要的事情。
当然在该系统的设计与实现的过程中也离不开老师以及同学们的帮助，正是因为他们的指导与帮助，我才能够成功的在预期内完成了这个系统。同时在这个过程当中我也收获了很多东西，此系统也有需要改进的地方，但是由于专业知识的浅薄，并不能做到十分完美，希望以后有机会可以让其真正的投入到使用之中。
[1]陈燕帆,官文兵. 一种关于mysql数据库的本地用户访问审计方法[P]. 广东省：CN114328455A,2022-04-12.
[2]王春丽.基于SSM框架的会议管理信息系统设计与实现[J].电脑编程技巧与维护,2022(03):83-85.DOI:10.16184/j.cnki.comprg.2022.03.016.
[3]戴靓婕.MySQL数据库在自动测试系统中的应用研究[J].长江信息通信,2022,35(03):162-164.
[4]王常珏,段尧清,朱泽.基于SSM的政府数据治理联盟链框架构建[J/OL].情报科学:1-18[2022-04-21].http://kns.cnki.net/kcms/detail/22.1264.g2.20220309.1213.002.html
[5]吴明阳,王森琛.基于SSM框架整合的客户服务系统设计和实现[J].新型工业化,2022,12(02):12-15.DOI:10.19335/j.cnki.2095-6649.2022.02.005.
[6]张文慧,王国田,陈永,温禾,袁涛,艾显威.基于SSM框架城市水体治理工程案例信息系统设计与实现[J].软件,2022,43(02):83-88+92.
[7]李双,郭晨晨,李佳虎,张慧娥.基于SSM框架的智能驾校系统的设计与开发[J].电脑知识与技术,2022,18(03):62-63+65.DOI:10.14004/j.cnki.ckt.2022.0150.
[8]王慧芳,孙方,陈玉,朱茜.基于SSM框架的大数据个性化推荐系统设计[J].信息与电脑(理论版),2022,34(02):90-92.
[9]郭静.基于SSM框架的高校新生预报到系统的设计与实现[J].电子技术与软件工程,2022(02):232-235.
[10]徐旭,李明明,夏辉,陈曦,王天宇,肖硕,雍旭.基于SSM框架的互联网+多元监管下构建医疗设备质量控制管理服务平台研究[J].中国医学装备,2021,18(12):106-110.
[11]张洁,张圆梦.基于改进F-AHP的牙科诊所选址合理性研究[J].经营与管理,2022(01):78-84.DOI:10.16517/j.cnki.cn12-1034/f.2022.01.006.
[12]师晨昊,宋谊深,师悦祺,张馨月. 一种用于牙科诊所的电脑管理系统[P]. 河北省：CN213122754U,2021-05-04.
[13]吴晓旭.经济背景下牙科诊所信息系统的分析与设计[J].营销界,2020(35):182-184.
[14]Khan Mahnoor,Soltau Rhea,Sea Juehwan,Sofjan Amelia K. 2078. Patterns, Indications, and Appropriateness of Antibiotics Prescribed at a Private Dental Practice[J]. Open Forum Infectious Diseases,2019,6(Supplement2).
[15]Nikolaus Palmer,Henry Clover. A Pilot Study to Investigate Antibiotic Prescribing in Private Dental Practice in the UK[J]. Primary Dental Journal,2019,8(1).
[16]Jean Gillian,Holden Alexander C L,Tennant Marc,Kruger Estie. Infection Control Standards in Private Dental Practice - The Role of Accreditation.[J]. Journal of law and medicine,2018,25(4).
[17]肖睿,程宁,田崇峰,金志雄,杜毅. MySQL数据库应用技术及实战[M].人民邮电出版社:, 201801.177.
[18]罗蓓蕾. K公司在中国私立牙科诊所的营销策略研究[D].上海交通大学,2017.DOI:10.27307/d.cnki.gsjtu.2017.001276.
致 谢
逝者如斯夫，不舍昼夜。转眼间，大学生会员活便已经接近尾声，人面对着离别与结束，总是充满着不舍与茫然，我亦如此，仍记得那年秋天，我迫不及待的提前一天到了学校，面对学校巍峨的大门，我心里充满了期待：这里，就是我新生活的起点吗？那天，阳光明媚，学校的欢迎仪式很热烈，我面对着一个个对着我微笑的同学，仿佛一缕缕阳光透过胸口照进了我心里，同时，在那天我认识可爱的室友，我们携手共同度过了这难忘的两年。如今，我望着这篇论文的致谢，不禁又要问自己：现在，我们就要说再见了吗？
感慨莫名，不知所言。遥想当初刚来学校的时候，心里总是想着工科学校会过于板正，会缺乏一些柔情，当时心里甚至有一点点排斥，但是随着我对学校的慢慢认识与了解，我才认识到了她的美丽，她的柔情，并且慢慢的喜欢上了这个校园，但是时间太快了，快到我还没有好好体会她的美丽便要离开了，但是她带给我的回忆，永远不会离开我，也许真正离开那天我的眼里会满含泪水，我不是因为难过，我只是想将她的样子映在我的泪水里，刻在我的心里。最后，感谢我的老师们，是你们教授了我们知识与做人的道理；感谢我的室友们，是你们陪伴了我如此之久；感谢每位关心与支持我的人。
少年，追风赶月莫停留，平荒尽处是春山。
点赞+收藏+关注 → 私信领取本源代码、数据库