Table of contents
1.3 Introduction to B/S architecture
1. 4 Introduction to ASP.NET Framework
2 Analysis of medical record management system
2.2.2Data modification process 5 _ _ _ _
2. 2. 3 Data deletion process 5 _ _
2.3 System Function Analysis 6
2.3.2 Non-functional analysis 6
2.4 System use case analysis 7
2.5 Summary of this chapter 10
3 Overall design of medical record management system 11
3.1 System architecture design 11
3. 2.1 Conceptual structure design of database
3. 2.2 Database logical structure design
3. 3 Summary of this chapter 22
4Design and implementation of key modules of medical record management system 2 3
4. 3Patient Management Module 31
4. 6Pick-up information module 32
4. 7 Prescription Information Module 32
5.1 The significance of system testing
The rapid development of scientific and technological progress has caused tremendous changes in people's daily lives. The rapid development of electronic information technology has made the application level of electronic information technology in various fields popular and applied. The arrival of the information age has become an unstoppable fashion trend, and the history of human development is entering a new era. In actual application, the working rules and development steps of the application software are used to build a medical record management system using ASP.NET technology.
This design mainly implements a medical record management system that combines the advantages of humanization, high efficiency, convenience, etc., and completes user management (administrators, doctors, nurses) module management (departments, patient medical records, drug warehouses, prescription information, medicine picking information, patient management) and other functional modules. The system communicates with the server through the browser to realize data interaction and changes. This system improves work efficiency and reduces errors and omissions in data storage through scientific management methods and convenient services. The medical record management system uses C# language, is developed using ASP.NET technology based on the MVVM model, and is written using a visual compiler. In terms of data, it mainly uses Microsoft's SQL Server relational database as the data storage medium, and cooperates with ASP.NET technology. Complete system development.
Keywords : ASP.NET technology; SQL Server; medical record management system
Abstract
The rapid development of technology has caused tremendous changes in people's daily lives, and the rapid development of electronic information technology has popularized and applied the application level of electronic information technology in various fields. The arrival of the information age has become an unstoppable fashion trend, and the history of human development is entering a new era. In practical applications, the working rules and development steps of the application software are constructed using ASP. NET technology to build a medical record management system.
This design mainly implements a medical record management system that combines the advantages of humanization, efficiency, and convenience, and completes functional modules such as user management (administrator, doctor, nurse) module management (department, patient medical record, drug warehouse, prescription information, drug picking information, and patient management). The system communicates with the server through a browser to achieve data interaction and changes. This system improves work efficiency and reduces errors and omissions in data storage through scientific management and convenient services. The medical record management system uses C # language, adopts the search ASP.NET technology based on MVVM mode for development, and uses the visual compiler to compile. In terms of data, Microsoft's SQL Server relational database is mainly used as the data storage medium, and the system development is completed with ASP.NET technology.
Keywords:ASP. NET technology; SQL Server； Medical Record Management System
1 Introduction
1.1 Research background
In multiple medical technology application scenarios such as clinical diagnosis, medical health care, disease prevention, disease source control, and health supervision, medical records, as the carrier of medical information throughout the patient's entire life cycle, have always played an irreplaceable and important role. Information technology has been fully developed in the 21st century, and has comprehensively changed and subverted people's lives through integration with traditional industries. Traditional industries have also adapted to the requirements of the times and joined the torrent of informatization and automation development. The storage form of medical records, a carrier of medical information, has gradually changed from traditional paper and film to electronic information. In addition, medical records also have many characteristics such as complex types, various contents, high degree of correlation, and huge amount of data. The traditional electronic information storage method is far from meeting the needs. In clinical practice, it is necessary to introduce methods that are more in line with the current situation. The need for medical record management systems has become particularly urgent.
With the promulgation of new medical reform plans such as the "Opinions on Deepening the Reform of the Medical and Health System" (hereinafter referred to as the "Opinions") and the "Implementation Plan for Deepening the Reform of the Medical and Health System from 2009 to 2011", my country has also officially begun to carry out reforms in the medical field. reform. Among them, the information reform of medical institutions is one of the eight supporting systems for this new medical reform. In the "Opinions", the state clearly requires medical institutions to implement informatized management and information sharing of the large amounts of medical data generated every day. Medical informatization has laid the foundation for the reform of my country's medical and health system and the promotion of the development of medical technology.
Standardization and information management of the medical system require the use of advanced technologies to achieve the purpose of improving medical standards, reducing medical costs, and improving the medical system. Some developed countries abroad have taken the lead in proposing relevant reform policies and completing their implementation. Therefore, their policies and response guidelines also provide certain reference for the reform of my country's medical system. For this purpose, we can base on foreign prior research results and combine China's national conditions with research results to ultimately achieve the standardization and informatization of the medical system with Chinese characteristics. The development of informatization can effectively improve the overall level of my country's medical care, which is of great strategic significance to patients, medical institutions and the country.
At present, hospitals in our country have successively established medical record management systems that can greatly improve the efficiency of medical record management of medical personnel and reduce unnecessary manpower consumption. To a certain extent, they have realized the informatization construction of hospital development. However, with the development of the economy, people's quality requirements for medical services have gradually increased, and the types and quantities of hospital business have also increased with it. As a result, many medical record management systems in current hospitals can no longer handle the collection and organization of medical record-related data. And storage and other major tasks, the use of resources has gradually deviated from the needs of the times and related standards. In order to get the utilization of information resources back on track, relevant researchers and medical institutions must design and implement a reasonable medical record management system based on the actual situation of the hospital and the actual needs of modern users to support the healthy and stable development of the medical industry and improve medical institutions. The quality and efficiency of serving patients.
1.2 Research significance
The significance of research on the medical record management system is not only because national policies have put forward new requirements for clinical diagnosis and treatment, but also to improve the country's overall medical level, improve the medical record management efficiency of medical staff, provide patients with more scientific and reasonable medical services, and achieve the goals of medical institutions. Comprehensive informatization. As an indispensable part of hospital information construction, the medical record management system is of far-reaching significance to the whole people, society and the future development of the country. Specifically, it can be divided into the following four points:
(1) Improve work efficiency and service quality. The promotion of the medical record management system can provide strong support for the daily work of medical staff, such as standardizing and unifying the format of medical records through the standardized medical record input function module; reducing the error rate of medical record transcription to close to zero through the automatic sharing function module of medical records. ; The implementation of paperless office can improve the efficiency of medical applications, examinations and feedback; the combination with cyberspace can assist doctors in diagnosing patients and provide reasonable suggestions when doctors formulate treatment plans.
(2) Realize information sharing. The medical record management system based on ASP.NET technology has good big data storage capabilities and can easily and quickly transmit and share all patient treatment information. In addition, the medical record management system based on ASP.NET technology has good compatibility and is easy to use. Promote it in major medical institutions to achieve the role of information unification. It is expected to play a greater role in the subsequent medical information management process and help patients seamlessly transfer their medical information to the medical records of the patient's new hospital. Management system to gain valuable treatment time for patients.
(3) Improve the overall management level of the hospital. The traditional medical record management process is divided into link management and terminal management. That is to say, the medical office needs to archive discharge medical records within seven days, conduct quality inspections of existing medical records from time to time, and conduct quality inspection results every month. Summary report. It can be seen that the above process has caused a huge waste of labor costs. Therefore, the introduction of a medical record management system that can collect and feedback various historical data in a timely manner is expected to standardize and unify medical record management, achieve standardized system management, and thereby improve the medical record management level of all medical institutions.
(4) Assist national medical macro-management. The promotion of medical record management systems is expected to provide richer information resources for national medical macro-management, thereby promoting relevant national departments to formulate more reasonable, scientific and sustainable development management policies, and realize the value extraction process of converting data into information. Through accumulated patient data, we can effectively prevent and predict patients, helping to improve the level of data-based and informatized medical care in our country. By combining the latest research such as data mining and artificial intelligence, we can improve the level of medical management in our country and further improve The efficiency of my country’s medical resources.
1.3 Introduction to B/S architecture
B/S structure (Browser/Server, browser/server mode) is a network structure mode after the rise of WEB. The WEB browser is the most important application software on the client. This model unifies the client and concentrates the core parts of system function implementation on the server , simplifying the development, maintenance and use of the system. Just install a browser on the client, such as Chrome , Safari , Microsoft Edge , Netscape Navigator or Internet Explorer , and install SQL Server , Oracle , SQL Server and other databases on the server. The browser interacts with the database through the Web Server .
1.4 Introduction to ASP.NET framework
ASP.NET, also known as ASP+ , is not just a simple upgrade of ASP, but a new generation scripting language launched by Microsoft. ASP.NET is a Web development platform based on the .NET Framework. It not only absorbs the greatest advantages of previous versions of ASP and adds many new features based on the development advantages of Java and VB languages, but also corrects the running errors of previous ASP versions.
ASP.NET has all the solutions for developing website applications, including all functions such as validation, caching, state management, debugging and deployment. In terms of code writing, the feature is to separate page logic and business logic. It separates program code and displayed content, making it easier to write colorful web pages. At the same time, the program code looks cleaner and simpler.
1.8.1 Hardware environment
The operation of the .NET platform has the following hardware requirements:
①Computer/ processor .
Recommended configuration: PC with 450 MHz Pentium II class processor.
Minimum configuration: PC with 300 MHz Pentium II level processor, otherwise the compilation process will run extremely slowly.
②Minimum requirements for RAM.
Windows XP Professional：160 MB RAM。
Windows 2000 Professional：96 MB RAM。
Windows 2000 Server：192 MB RAM。
Windows NT 4.0 Workstation：64 MB RAM。
Windows NT 4.0 Server：160 MB RAM。
③Hard disk: The standard version requires 2.5GB on the installation drive, including 500MB on the system drive.
Professional and Enterprise editions require .5GB on the installation drive, including 500MB on the system drive. If you do not need the reference documentation in Microsoft Visual Studio.NET and only need to support C# development, you will need at least about 700M of space.
④Drive: CD-ROM or DVD-ROM drive, used to use CDs to install development platform programs. Of course, this is not absolute, and you can completely choose the network installation method.
⑤Monitor: SuperVGA (800×600) or a higher resolution 256-color monitor. In fact, it is recommended to use a resolution of 1024×768 or above, otherwise the development process will be inconvenient because the visual range is too small.
⑥Input device: MjcrosoR mouse or compatible pointing device.
Of course, the hardware requirements pointed out here are not absolute. If conditions permit, you should choose a machine with a higher configuration, which is very helpful for development.
①Operating system: MicrosoR Windows NT 4. O or higher operating systems, including Microsoft windows2000 series, Microsoft windows 2003 series, do not support Microsoft Windows 95, Microsoft windows 98, Microsoft windows Me and other operating systems.
Note: Microsoft Windows NT 4.0 needs to be upgraded to SP6 or above. For operating systems above Windows 2000, you need to upgrade Windows 2000 to SP3 or later.
②Framework: Framework is the supporting foundation of .NET. It contains the runtime library of the .NET platform and the common language runtime. All programs under the .NET platform need to be built based on its class library, and all programs need to be compiled into intermediate language (IL) first and then used by the common language. The language runtime manages execution. It can be said that without Framework, there would be no .NET platform.
For the development of .NET, Microsoft has also prepared many development tools for developers, which are integrated into the Framework SDK. To develop .NET, these development and debugging tools are indispensable. Therefore, to carry out .NET development, it is best to install the Framework SDK.
However, it should be noted that the Microsoft Windows 2003 series has integrated Framework (but does not include Framework SDK). Unless there is a new version, there is generally no need to install it again. In addition, the counterpart to Framework under Linux is Mono.
③MDAC: With the above mentioned, you already have the most basic .NET development platform, which can be used to develop some simple programs. However, when objects such as databases and XML are to be used, the written program may not be executed.
Because .NET still has basic needs - MDAC (Microsoft Data Access CompHDnents), which is translated into Chinese as Microsoft Data Access Components. This is a complete set of Microsoft data access components. Almost all database access under the Windows platform is completed by these components. Therefore, MDAC is an indispensable part for .NET database development.
AdobeDreamweaver
MicrosoftExpression Web
MicrosoftWebMatrix
Notepad++
EditPlus
2 Analysis of medical record management system
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. Then, a feasibility analysis is performed on the system development, which usually includes technical feasibility, economic feasibility, etc. The feasibility analysis is also an analysis from the overall perspective of the project. Then the specific requirements of the project are analyzed. The analysis method is generally implemented through the user's use case diagram. The following is a detailed introduction.
2.1 Feasibility analysis
(1) Technical feasibility analysis
The medical record management system uses a SQL Server database for storage and visual for development . These development tools can bring a lot of convenience to our writing work. The system is developed using the ASP.NET framework, which makes the system more scalable and maintainable, reduces ASP.NET configuration code, and simplifies programming code. Currently, the ASP.NET framework is also one of the frameworks chosen by many enterprises.
(2) Economic feasibility analysis
The development software used in developing the medical record management system, such as visual development tools, Tomcat8.0 server, SQL Server 5.7 database, Photoshop image processing software, etc., are all open source and free. These environments have been systematically studied in the school. You can operate it independently without any additional cost, and the system development tools can be downloaded directly from the Internet, so it is economically feasible.
(3) Operation feasibility analysis
When designing this project, I referred to many successful cases of similar systems, systematically analyzed their operation interfaces and functions, and combined many cases together to highlight people-oriented and simplified operations, so people with basic computer knowledge can Operate this project. Therefore, there is no problem with operational feasibility.
2.2 System process analysis
The business process uses some specific symbols and lines to demonstrate the user's process when using the system. When performing system analysis, the business process can help developers better understand the business, discover errors, and improve the system.
2.2.1 Data augmentation process
After the user successfully logs in to the system , he or she can add data. The number of the added data is specific and generated by the system. The user cannot fill it in at will. Except for the number, the user fills in other added information by himself. The filled-in information is verified by the system and is legal. If it passes, it will show that the data has been added successfully. If it is passed, it will not be added successfully. Figure 2-1 shows the process of adding data.
Figure 2-1 Data addition flow chart
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 is some useless data in the system , the relevant managers can also delete the data. Figure 2-3 is the flow chart for data deletion.
Figure 2-3 Data deletion flow chart
2.3 System function analysis
The design and implementation of the medical record management system is to make it more convenient for users to manage some information related to employees . It can save a lot of time and energy when users search and manage, and effectively reduce unnecessary search time. The system is functionally divided into three parts: administrators, nurses and doctors .
Nurse:
(1) Login: Users can log in through the account and password in the background. The user's account and password are added by the administrator. If you forget your password, you can click "Forgot Password" to retrieve your password;
(2) Prescription information: Click the "Prescription Information" menu to view all prescription information added in the system. It supports querying prescription information by prescription number or drug number or drug name. If you want to know the details of a certain prescription Information, click "Details" at the back to enter the details interface. If you want to select a prescription, click the "Prescribe" button, fill in the corresponding information according to the prompts, and click the "Submit" button. If there are no errors in the information, it will be submitted to the database. Success, the prescription is successful;
(3) Drug Warehouse: Click the "Drug Warehouse" button to view the drug warehouse you submitted. It supports querying the drug warehouse by drug number or drug name or drug type. If you want to know the detailed information of a certain drug, click below "View" will enter the details interface;
(4) Patient management: Click the "Patient Management" button to view all patient management information submitted by you. It supports querying patient information by patient name or patient age. If you want to add new patient information, click "Add" button and then enter the patient information according to the prompts. After clicking "Submit", the new patient information will be displayed on the patient management interface. You can click on a certain patient management to view the details of the patient information;
administrator:
(1) Login: The administrator can log in through the account and password in the background. The administrator's account and password are set directly in the database. If you forget the password, you can click "Forgot Password" to retrieve the password;
(2) System users: Administrators can control all user roles in the system, including administrators, nurses, and doctors. If you need to add a new user, click the "Add" button on the page and enter according to the prompts. Go to the user information and click "Submit" to view it on the corresponding user interface. You can click the "Delete" button behind the user to directly delete a user.
(3) Patient management: When the administrator clicks "Patient Management", all patient information will be displayed. It supports inputting the patient's name or age to query the patient. If you want to add a new patient, click the "Add" button and enter the relevant information. , click the "Submit" button to add it. At the same time, you can select a certain piece of patient information and click "Delete" to delete it. You can also click the "Create Medical Record" button at the back to maintain the patient's established medical record information;
(4) Drug warehouse: Click the "Drug Warehouse" button to view all drug warehouses in the system. It supports querying drug warehouses by drug number or drug name. If you want to add a new drug warehouse, click the "Add" button , then fill in the specific information of the drug warehouse according to the prompts, click Submit and the added drug warehouse will be saved in the database. At the same time, you can click the "Prescribe Medicine" button and enter the prescribing doctor's information for submission, or you can choose to delete Drug warehouse directly clicks the "Delete button" to delete the drug warehouse.
(5) Patient medical records: Click the "Patient Medical Records" button to view all patient medical record information in the system. It supports querying patient medical record information by medical record number or patient age. If you want to add new patient medical record information, click "Add" " button and then enter the patient's medical record information according to the prompts. After clicking "Submit", the new patient's medical record information will be displayed on the patient medical record interface. You can click on a certain patient's medical record information to view the details of the patient's medical record information, or you can directly click "Delete" "To delete patient medical records;
(6) Prescription information: Click the "Prescription Information" button to view all prescription information in the system. It supports querying prescription information by drug number or drug name or drug type. If you want to add new prescription information, click "Add" " button and then enter the prescription information according to the prompts. After clicking "Submit", the new prescription information will be displayed on the prescription information interface. You can click on a certain prescription information to view the details of the prescription information, or you can directly click "Delete" to delete the prescription. information;
(7) Drug Picking Information: Click the "Drug Picking Information" button to view all drug picking information in the system. It supports querying drug picking information by prescription number or drug number. If you want to add new drug picking information, click "Add" button and then enter the medicine picking information according to the prompts. After clicking "Submit", the newly added medicine picking information will be displayed on the medicine picking information interface. You can click on a certain medicine picking information to view the details of the medicine picking information, or you can directly Click "Delete" to delete the medicine picking information;
2.3.2 Non-functional analysis
The non-functional requirements of the medical record management system include the security, reliability, performance, scalability, etc. of the medical record management system. The details can be expressed in the following 3-1 table:
Table 3-1 Non-functional requirements table of medical record management system
| safety |
Mainly refers to the installation of the medical record management system database, the use of the database and the setting of passwords must comply with standards. |
| reliability |
Reliability means that the medical record management system can be operated according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for the medical record management system to occupy the market, so it is best to have good performance. |
| 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 page display content of the medical record management system and operate. |
| maintainability |
The maintainability of medical record management system development 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 this medical record management system is obtained:
An example of the nurse role is shown in Figure 2-3.
Figure 2-3 Use case diagram of nurse role in medical record management system
The administrator on the web background management maintains all data information in the entire medical record management system. An example of the administrator role is shown in Figure 2-4.
figure 2-4 Use case diagram of the role of medical record management system administrator
This chapter mainly determines the functions to be realized by the entire medical record management system through feasibility analysis, process analysis, functional requirements analysis, and system use case analysis of the medical record management system. It also provides standards for code implementation and testing of medical record management systems.
3 Overall design of medical record management system
The main contents discussed in this chapter include the functional module design and database system design of the medical record management system.
3.1 System architecture design
This medical record management system is divided into three layers in terms of architecture: presentation layer (UI), business logic layer (BLL) and data layer (DL).
Figure 3-1 Medical record management system architecture design diagram
Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of this medical record management system. A good UI can improve the user experience and enhance the user's comfort when using this medical record management system. The UI interface design must also adapt to different versions of medical record management systems and different size resolutions to achieve good compatibility. The UI interaction function requirements are reasonable, and users must obtain consistent interaction results when performing interactive operations. This requires the presentation layer to be well connected with the business logic layer.
Business logic layer (BLL): mainly completes the data processing function of this medical record management system. The data transmitted by the user from the presentation layer is processed by the business logic layer and delivered to the data layer. The data read by the system from the data layer is processed by the business logic layer and delivered to the presentation layer.
Data layer (DL): Since the data of this medical record management system is placed in the SQL Server database on the server side, the parts that belong to the service layer can be directly integrated into the business logic layer. Therefore, there is only the database in the data layer, which mainly completes this task. Data storage and management functions of the medical record management system.
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 this medical record management system were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of this medical record management system. The medical record management system is derived based on the demand analysis in the previous chapter, and its overall design module diagram is shown in Figure 3-2.
Figure 3-2 Function module diagram of medical record management system
Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.
3.3.1 Database conceptual structure design
The following is the overall ER entity relationship diagram of the main database tables in the entire medical record management system.
Figure 3-6 Overall ER relationship diagram of the medical record management system
3.3.2 Database logical structure design
From the previous ER diagram, you can see that the project requires the creation of many data tables. The following is the relational model of the main database tables in the project:
Table department (department)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
department_id |
int |
10 |
0 |
N |
Y |
Department ID |
|
| 2 |
department |
varchar |
64 |
0 |
Y |
N |
Department |
|
| 3 |
department_introduction |
longtext |
2147483647 |
0 |
Y |
N |
Department introduction |
|
| 4 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 5 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table doctor (doctor)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
doctor_id |
int |
10 |
0 |
N |
Y |
Doctor ID |
|
| 2 |
doctors_name |
varchar |
64 |
0 |
Y |
N |
Doctor's name |
|
| 3 |
department |
varchar |
64 |
0 |
Y |
N |
Department |
|
| 4 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 6 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table drug_warehouse (drug warehouse)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
drug_warehouse_id |
int |
10 |
0 |
N |
Y |
Drug warehouse ID |
|
| 2 |
drug_no |
varchar |
64 |
0 |
N |
N |
Drug number |
|
| 3 |
drug_name |
varchar |
64 |
0 |
Y |
N |
Drug Name |
|
| 4 |
drug_type |
varchar |
64 |
0 |
Y |
N |
Drug type |
|
| 5 |
drug_specifications |
varchar |
64 |
0 |
Y |
N |
drug specifications |
|
| 6 |
inventory_quantity |
int |
10 |
0 |
Y |
N |
0 |
Stock quantity |
| 7 |
sales_unit_price |
int |
10 |
0 |
Y |
N |
0 |
Sales unit price |
| 8 |
drug_details |
longtext |
2147483647 |
0 |
Y |
N |
Drug details |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 11 |
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 |
Y |
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 |
Y |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table medication_picking_information (picking medicine information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
medication_picking_information_id |
int |
10 |
0 |
N |
Y |
Pick up medicine information ID |
|
| 2 |
prescription_number |
varchar |
64 |
0 |
N |
N |
prescription number |
|
| 3 |
drug_no |
varchar |
64 |
0 |
Y |
N |
Drug number |
|
| 4 |
drug_name |
varchar |
64 |
0 |
Y |
N |
Drug Name |
|
| 5 |
drug_type |
varchar |
64 |
0 |
Y |
N |
Drug type |
|
| 6 |
drug_specifications |
varchar |
64 |
0 |
Y |
N |
drug specifications |
|
| 7 |
sales_unit_price |
int |
10 |
0 |
Y |
N |
0 |
Sales unit price |
| 8 |
doctor |
int |
10 |
0 |
Y |
N |
0 |
doctor |
| 9 |
responsible_nurse |
int |
10 |
0 |
Y |
N |
0 |
nurse in charge |
| 10 |
number_of_prescriptions |
int |
10 |
0 |
Y |
N |
0 |
Number of medicines prescribed |
| 11 |
drug_amount |
varchar |
64 |
0 |
Y |
N |
Drug amount |
|
| 12 |
prescription_date |
date |
10 |
0 |
Y |
N |
Prescription date |
|
| 13 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
Medical record number |
|
| 14 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 15 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 16 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
table nurse (nurse)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
nurse_id |
int |
10 |
0 |
N |
Y |
Nurse ID |
|
| 2 |
name_of_nurse |
varchar |
64 |
0 |
Y |
N |
nurse name |
|
| 3 |
department |
varchar |
64 |
0 |
Y |
N |
Department |
|
| 4 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 6 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table patient_management (patient management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
patient_management_id |
int |
10 |
0 |
N |
Y |
Patient Management ID |
|
| 2 |
patient_name |
varchar |
64 |
0 |
Y |
N |
patient name |
|
| 3 |
patient_age |
int |
10 |
0 |
Y |
N |
0 |
patient age |
| 4 |
patient_gender |
varchar |
64 |
0 |
Y |
N |
patient gender |
|
| 5 |
patient_medical_history |
varchar |
64 |
0 |
Y |
N |
patient history |
|
| 6 |
contact_number |
varchar |
16 |
0 |
Y |
N |
contact number |
|
| 7 |
patients_address |
varchar |
64 |
0 |
Y |
N |
patient address |
|
| 8 |
patient_condition |
text |
65535 |
0 |
Y |
N |
patient status |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table patient_medical_record (patient medical record)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
patient_medical_record_id |
int |
10 |
0 |
N |
Y |
Patient medical record ID |
|
| 2 |
medical_record_number |
varchar |
64 |
0 |
N |
N |
Medical record number |
|
| 3 |
patient_name |
varchar |
64 |
0 |
Y |
N |
patient name |
|
| 4 |
patient_age |
int |
10 |
0 |
Y |
N |
0 |
patient age |
| 5 |
patient_gender |
varchar |
64 |
0 |
Y |
N |
patient gender |
|
| 6 |
contact_number |
varchar |
16 |
0 |
Y |
N |
contact number |
|
| 7 |
patient_medical_history |
varchar |
64 |
0 |
Y |
N |
patient history |
|
| 8 |
patient_medical_record |
varchar |
255 |
0 |
Y |
N |
patient records |
|
| 9 |
medication_record |
longtext |
2147483647 |
0 |
Y |
N |
Medication records |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 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 prescription_information (prescription information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
prescription_information_id |
int |
10 |
0 |
N |
Y |
Prescription information ID |
|
| 2 |
prescription_number |
varchar |
64 |
0 |
Y |
N |
prescription number |
|
| 3 |
drug_no |
varchar |
64 |
0 |
Y |
N |
Drug number |
|
| 4 |
drug_name |
varchar |
64 |
0 |
Y |
N |
Drug Name |
|
| 5 |
drug_type |
varchar |
64 |
0 |
Y |
N |
Drug type |
|
| 6 |
drug_specifications |
varchar |
64 |
0 |
Y |
N |
drug specifications |
|
| 7 |
sales_unit_price |
int |
10 |
0 |
Y |
N |
0 |
Sales unit price |
| 8 |
doctor |
int |
10 |
0 |
Y |
N |
0 |
doctor |
| 9 |
responsible_nurse |
int |
10 |
0 |
Y |
N |
0 |
nurse in charge |
| 10 |
number_of_prescriptions |
int |
10 |
0 |
Y |
N |
0 |
Number of medicines prescribed |
| 11 |
drug_amount |
varchar |
64 |
0 |
Y |
N |
Drug amount |
|
| 12 |
prescription_date |
date |
10 |
0 |
Y |
N |
Prescription date |
|
| 13 |
medical_record_number |
varchar |
64 |
0 |
Y |
N |
Medical record number |
|
| 14 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 15 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 16 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table upload (file upload)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
Upload ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
file name |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
access path |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
file path |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
display order |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
Parent ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
folder |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
file type |
Table user (user account: used to save user login information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
User ID: [0,8388607] User obtains other user-related data |
|
| 2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
Account status: [0,10](1 available | 2 abnormal | 3 frozen | 4 logged out) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
User group: [0,32767] determines user identity and permissions |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Last Login Time: |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
Mobile phone number: [0,11] User’s mobile phone number, used to retrieve password or log in |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
Mobile phone certification: [0,1] (0 not certified | 1 under review | 2 certified) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
Username: [0,16] The account name used by the user to log in |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成 |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱：[0,64]用户的邮箱，用于找回密码时或登录时 |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证：[0,1](0未认证|1审核中|2已认证) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
表user_group (用户组：用于用户前端身份和鉴权)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID：[0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序：[0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
名称：[0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该用户组的特点或权限范围 |
|
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
3.4本章小结
整个病历管理系统的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4.1登录模块
管理员、医生和护士在登录界面输入账号+密码，点击“登录”按钮，系统在用户数据库表中会对管理员和护士的账号进行匹配，账号+密码正确的话，就会登录到系统中各个用户的主管理界面，否则提示对应的信息，返回到登录的界面，其主界面展示如下图4.1所示。
图4.1 登录界面图
4.2科室模块
管理员和护士点击“科室”这个按钮可以查看到系统中的科室信息，支持通过科室进行查询科室信息，如果想要添加新的科室信息，点击“添加”按钮然后根据提示输入科室信息，点击“提交”后，在科室界面就会显示新增的科室信息，可以点击某一科室信息查看科室信息的详情，也可以直接点击“删除”进行删除科室。界面如下图4.2所示。
图4.2科室界面图
4.3患者管理模块
点击“患者管理”这个按钮可以查看到自己提交的患者管理，支持通过患者姓名或者患者性别进行查询患者管理，如果想要了解某一患者的详细信息，点击后面的“查看”会进入详情界面，也支持对自己选择的患者进行删除；医生和管理员可以对护士提交的患者进行病历添加，选择某一患者，点击后面的“病历”按钮，根据提示输入对应的信息，点击“提交”后，病历就录入成功了。界面如下图4.3所示。
图4.3 患者管理界面图
4.4药品仓库模块
点击“药品仓库”这个菜单，可以查看到系统中所有添加的药品仓库，支持通过药品编号或者药品名称或者药品类型对药品仓库进行查询，如果想要了解某一药品的详细信息，点击后面的“详情”会进入详情界面，医生和管理员如果想要选择某一药品仓库，点击“开药”按钮，根据提示填写对应的信息，点击“提交”按钮，信息没有错误在数据库就会提交成功，开药成功。界面如下图4.4所示。
图4.4 药品仓库界面图
4.5患者病历模块
点击“患者病历”这个按钮可以查看到系统中的患者病历信息，支持通过病历号或者患者姓名或者患者年龄进行查询患者病历信息，如果想要添加新的患者病历信息，点击“添加”按钮然后根据提示输入患者病历信息，点击“提交”后，在患者病历界面就会显示新增的患者病历信息，可以点击某一患者病历信息查看患者病历信息的详情，也可以直接点击“删除”进行删除患者病历。界面如下图4.4所示。
图4.5患者病历界面图
4.6捡药信息模块
点击“捡药信息”这个菜单，可以查看到系统中所有添加的捡药信息，支持通过处方号或者药品编号或者药品名称对捡药信息进行查询，只有管理员用户可以添加新的捡药信息，点击“添加”按钮，根据提示输入捡药信息，点击“提交”按钮，新的捡药信息就在系统中显示出来了，也可以对添加的捡药信息进行删除。界面如下图4.6所示。
4.7处方信息模块
点击“处方信息”这个菜单，可以查看到系统中所有添加的处方信息，支持通过处方号或者药品编号或者药品名称或者药品类型对处方信息进行查询，只有管理员用户可以添加新的处方信息，点击“添加”按钮，根据提示输入处方信息，点击“提交”按钮，新的处方信息就在系统中显示出来了，也可以对添加的处方信息进行删除。界面如下图4.7所示。
图4.7 处方信息界面图
5系统测试
系统开发的最后一个步骤就是系统测试，系统测试也是整个系统十分重要的一个环节，测试的好坏关系到产品的发展。用户对软件的质量、性能和可靠性等需求就要通过测试来实现。测试过程要必须遵循严谨性、完善性、规范性的原则，测试的主要目的就是看看在系统运行中，是否会出现bug，然后对出现的bug进行调试，直到程序完美运行。但是软件的测试只能尽可能的减少bug，理论上来说是无法达到消除bug。但是bug越少，系统出错的几率就越低，用户使用起来也更方便、更安全。
近年来，软件包含测试从现在的检验当中来看，系统接近预期目标可能出现的问题，并对这些错误做出相应的修正，假如我们不进行早期的测试错误就会延续下去，最后所做出的成品就会有很大的困难。
我们要在这个测试的过程当中找出错误。测试成软件开发的主要一部分，自从有了程序的设计那天开始，它就成为了重要的组成部分。经过统计来看，软件测试可以占据这个系统45%的工作量，而在软件开发的成本当中，对于测试成本来说它包含了很多的测试工作。每个程序测试时都会出现和遇到错误。在整个程序的开发过程当中，人为去查找错误是非常复杂和困难的，所以我们一般都会找一些测试的工具来进行测试。
5.1系统测试的意义
随着现代信息的快速发展，在社会各大领域中已经都开始应用网络信息技术，在应用网络技术的同时人们也开始把软件的质量问题作为了一个重要焦点来关注，因为一个软件的好与坏它决定着这个系统在市场上的生存，所以我们必须要把软件质量来做好，这样才有一定的生存能力。对于用户来说它们首先选用的都是保证这个系统软件的质量问题，因为一个系统的软件质量决定着用户在后期上成本经济的问题。
5.2 测试方法
黑盒测试又被人们称作为功能测试，通常是在程序的接口来做一些测试的方法，它一般包括对程序的功能和使用的方法来做出一些数据的接受和输出，同时还可以做出正确的输出信息，并保证与外部信息的完整性。
白盒测试通常被人们称作为结构测试，在整个程序的结构和处理当中它是由程序当中的逻辑测试和检验程序来完成一些正确的工作。
具体的功能测试它是包括：系统的适用性、准确性、安全性等功能测试。
5.3测试分析
基于病历管理系统满足相关信息的管理需求，在设计时借鉴了国内外优秀网站的优点，从界面到系统设计都保证了管理员以及用户能够方便操作。系统的主要特点和优点归纳如下：
（1）本系统用的移置性和针对性都比较高，因为针对性高可以提供更好的服务而移置性可以在多个系统上运行，更给用户带来了极大的方便。
(2) The medical record management system is comprehensive in content and easy to manage. It can handle various errors and exceptions in a timely manner, thus avoiding many errors caused by users' careless operations. It is easy to operate, has a friendly user interface, and can access the Internet. Everyone can operate it very well.
After analyzing the above test results, it is found that all basic functions are complete, the operation is simple, the system operation performance is good, the system is safe and reliable, and it can promote the development of medical record management systems and has broad development prospects.
in conclusion
At this point, the medical record management system has been completed. A lot of preparations were made before development. During the design and development process of this system, I read and studied a lot of literature, from which I also gained a lot of valuable methods and design ideas. I have a lot of confidence in the system. Development also plays a very important role. The system development technologies are all familiar to me, such as Web, ASP.NET, C# technology, and SQL Server. These technologies were learned in previous studies, and many of them are designed The ideas and methods are all gained from the experience of continuous learning in the past. In fact, the workload is still relatively large for us, but it is precisely because of the previous accumulation and preparation that we can successfully complete this project. From this point of view, Accumulating experience and being prepared are very important things.
Of course, the design and implementation of this system would also be inseparable from the help of teachers and classmates. It is precisely because of their guidance and help that I was able to successfully complete this system within expectations. At the same time, I also learned a lot during this process. This system also has areas that need improvement. However, due to the shallow professional knowledge, it cannot be perfect. I hope that I will have the opportunity to put it into real use in the future.
[1]Li Bing. Design and application of medical quality management system based on electronic medical records[J]. Electronic Components and Information Technology, 2023,7(01):208-212+216.DOI:10.19772/j.cnki.2096- 4455.2023.1.048.
[2] Yan Weiping. Advantages and development strategies of electronic medical record management systems [J]. China Health Standards Management, 2023, 14(01): 11-14.
[3] Zou Guipeng, Ma Jianrong, Bai Lijun, Sun Huiming. Electronic medical record management system based on artificial intelligence [P]. Shaanxi Province: CN115565633A, 2023-01-03.
[4] Liu Shuqun. Design of electronic medical record management system based on cloud computing technology [J]. Wireless Internet Technology, 2022, 19(03): 61-62.
[5] Liu Weilan. Research on hospital medical record information management system based on J2EE [J]. Computer Programming Skills and Maintenance, 2021(12):79-80+96.DOI:10.16184/j.cnki.comprg.2021.12.029.
[6] Ma Zhonghong, Xianghesheng Pre-hospital Emergency Medical Record Data Electronic Management and Analysis System V3.0. Henan Province, Zhengzhou Xianghesheng Electronic Technology Co., Ltd., 2021-10-18.
[7] Tu Yinying. Effectiveness of medical quality management system construction based on structured electronic medical records [J]. Electronic Technology and Software Engineering, 2021(18):172-173.
[8] Chen Ying. Establishment and application of electronic special medical record management system for outpatient narcotic drugs [J]. Journal of Traditional Chinese Medicine Management, 2021, 29(17): 166-167. DOI: 10.16690/j.cnki.1007-9203.2021. 17.080.
[9] Yan Mingfei. Analysis on the application of electronic medical record system in hospital information management system [J]. Computer Knowledge and Technology, 2021, 17(18): 43-44. DOI: 10.14004/j.cnki.ckt.2021.1654.
[10] Ning Haitao. Automatic management method of university office documents based on ASP.NET technology [J]. Information and Computers (Theoretical Edition), 2020, 32(19): 10-11.
[11] Wang De'an, Liu Yannan. Research and implementation of basic operation methods of data tables based on jQuery+ASP.NET technology [J]. Computer Programming Skills and Maintenance, 2020(07):72-74+79.DOI:10.16184/j. cnki.comprg.2020.07.025.
[12]. A Development of Medical Records Management System to Health Care Decision Makers using Cloud Technologies[J]. International Journal of Engineering and Advanced Technology,2020,9(4).
[13] Shi Lei. Faculty evaluation system based on ASP.NET technology [J]. Computers and Networks, 2020, 46(06): 70-72.
[14]Joseph Bitrus,A. Wadzani,Maigana Ngubdo,E. Agu. Design and Implementation of a Secured Web based Medical Record Management System: A Case Study of Federal University Wukari (FUW) Clinic[J]. International Journal of Computer Applications,2020,177(41).
[15] Su Feng, Electronic medical record management system for internal medicine specialty. Henan Province, 83rd Army Hospital of the Chinese People's Liberation Army, 2019-10-22.
[16] Qi Youbo. Design and implementation of a hospital’s medical record management system [D]. University of Electronic Science and Technology of China, 2019.DOI:10.27005/d.cnki.gdzku.2019.000379.
[17] Muhammad Nabil Mohd Warid, Eko Supriyanto, Azli Yahya, Mohd Nizam Mat Bah, Ngim Chin Fang. Online framework for thalassemia medical record management system[J]. AIP Conference Proceedings,2019,2092(1).
[18] Ma Chao, Sha Jintao. Development of numerical wind tunnel experiment platform based on ASP.NET technology [J]. Education and Teaching Forum, 2018(35):277-278.
[19] Yan Chunfeng. Implementation of hospital appointment registration system based on asp.net technology [J]. Computer Knowledge and Technology, 2018, 14(12): 72-73. DOI: 10.14004/j.cnki.ckt.2018.1324.
Thanks
The deceased is like a man who never gives up day and night. In the blink of an eye, the life of a big user user is coming to an end. When people face parting and the end, they are always full of reluctance and confusion. I am also the same. I still remember that autumn, I couldn’t wait to arrive at school one day early, facing the school Looking at the majestic gate, I was full of expectations: Is this the starting point of my new life? That day, the sun was shining brightly, and the school's welcome ceremony was very warm. I faced my classmates who were smiling at me, as if rays of sunshine shone through my chest into my heart. At the same time, I met my lovely roommate that day, and we joined hands. We spent these two unforgettable two years together. Now, as I look at the acknowledgments of this paper, I can’t help but ask myself: Are we saying goodbye now?
I feel inexplicable and don't know what to say. I remember when I first came to school, I always thought that the engineering school would be too rigid and lack some tenderness. At that time, I was even a little bit repelled. But as I slowly got to know and understand the school, I realized that Her beauty, her tenderness, and I slowly fell in love with this campus, but time passed so quickly that I had to leave before I could fully appreciate her beauty, but the memories she brought to me will never be forgotten. If she leaves me, maybe my eyes will be filled with tears on the day she truly leaves. It’s not because I’m sad, I just want her image to be reflected in my tears and engraved in my heart. Finally, I would like to thank my teachers for teaching us knowledge and principles of life; thank you to my roommates for staying with me for so long; thank you to everyone who cares and supports me.
Young man, chase the wind and the moon without stopping. Wherever there is plain wasteland, there are spring mountains.
Please follow and like + privately message the blogger to receive the project source code for free