Design and implementation of drug management system based on Java Web

Note: Show part of the document content and system screenshots. If you need complete videos, codes, articles and installation and debugging environment, please send a private message to the up owner.

4 Design of medical information management platform

4.1 System design principles

In system design, practicality, safety and ease of operation are three important design principles. The principle of practicality emphasizes that the system must be practical, and user experience is the starting point of design. The system interface design should be user-friendly so that users can operate the system more conveniently and efficiently. During the testing process, examples should be selected for testing based on user needs to ensure that the system can meet user needs and solve actual problems.

4.2 System requirements analysis

This system was developed to assist in the management of drug management in individual pharmacies. It is also designed to help users manage medical information management platforms or administrators to manage information such as medical information management platforms. Therefore, the system must achieve medical information management. The platform or users can browse information such as drug management of individual pharmacies. The system must also have an administrator role to operate the administrator's functions, such as viewing the user's individual pharmacy drug management status.

Security principles are issues such as security and privacy that must be taken into consideration during system design. Strengthen factors such as account security, information security, and anti-intrusion security to ensure that user information will not be leaked. The system should be designed from the user's perspective, take user feedback promptly and seriously, and respond effectively to feedback.

The principle of ease of operation is that system design should give priority to ease of operation. The purpose of designing the program is to enable users to solve tedious problems more conveniently and efficiently. If there are more steps or higher difficulty, the system will lose its original value. Therefore, the program should be designed to be easy to operate so that users can use it easily.

4.3 Working principle of the system

The working principle diagram of this system is shown in Figure 5.

4.4 System function operation process

4.4.1 Login sequence diagram

The basic function of this module is login. Before users and administrators enter the system, select login and write down the specified data to complete the login. The user login sequence diagram is shown in Figure 6.

4.4.2 Personal Center Module

The basic function of this module is information management, information management after entering the personal center. The timing diagram of the personal center module is shown in Figure 7.

4.6.1 Database logical design

The purpose of database logical design is to convert the conceptual structure E-R diagram into a logical structure suitable for the database management system. Typically, people do this using a relational database such as Oracle or MySQL. Designing a logical structure usually requires following the following steps:

(1) Convert the E-R diagram into a relational model: Convert the entities and relationships in the E-R diagram into data tables and relationships in the relational database

(2) Convert to a data model supported by the specified database supervision system according to the characteristics and constraints of the specific database supervision system: According to the requirements of the specific database supervision system, design a data model suitable for the system.

(3) Optimize entity attributes: Optimize entity attributes to better support the database supervision system. This usually involves reducing entity properties to a minimum and ensuring that all properties are necessary.

Since the real-life information described by users may contain a lot of repeated and redundant information, 3NF reduction is required. 3NF reduction is the reduction of information to a minimum while maintaining data independence. When performing 3NF reduction, it is often necessary to minimize dependent dependencies to ensure that one database table does not contain non-primary key information that is already contained in other tables.

After optimization processing of the database's three normal forms (3NF), the logical structure table of the system can be obtained. As follows:

User (primary key ID, name, password, age, ID number, gender, phone number)

Individual pharmacy drugs (primary key, individual pharmacy drug number, individual pharmacy drug name, picture)

Configuration (primary key, name, parameter value)

Administrator (primary key ID, name, password, age)

4.6.2 Database physical design

Physical design is the process of further designing the database table structure based on the entity attributes obtained from the logical design. In order to achieve demand restrictions, the table structure usually sets corresponding constraints. Whether the table structure design is reasonable directly affects the performance of the system and the efficiency of later maintenance and updates. Therefore, the design of the table structure needs to be carefully considered in the physical design to ensure the stability and efficiency of the system.

Table 1 User table

Field	type	Field description	Remark
Id	Int	primary key	self-increasing
Username	Varchar(50)	username	non empty
Pass	Varchar(30)	password	non empty
Sex	Varchar(30)	gender	Default is 1
addtime	Date	add time	Follow system time
age	Char	age
phonenumber	Varchar(50)	Telephone

Table 2 Configuration table

Field	type	Field description	Remark
Id	Int	primary key	self-increasing
Name	Varchar(50)	name	non empty
value	Varchar(30)	Parameter value

Table 3 Drug list of individual pharmacies

Field	type	Field description	Remark
Id	Int	primary key	self-increasing
Addtime	Date	add time	non empty
name	Varchar(30)	name	non empty
picture	Varchar(30)	picture
number	Varchar(30)	serial number	non empty
classification	Char	category	non empty

Table 4 token table

Field	type	Field description	Remark
Id	bigint	primary key	self-increasing
userid	bigint	user id	non empty
username	varchar(100)	username	non empty
tablename	varchar(100)	Table Name
role	varchar(100)	Role	non empty
token	varchar(100)	password	non empty
addtime	timestamp	add time	non empty
expiratedtime	timestamp	Expiration	non empty

5 Implementation of system functions

5.1 Implementation of administrator terminal functions

The administrator port is the port with the highest authority and the most functions in this system. A representative display of this system can be made. The following content will use the internal implementation page and specific flow chart of the system to give a simple explanation of the administrator-side functions.

5.1.1 Implementation of administrator login function

The administrator logs in to the system to achieve management authority over system information. The login verification consists of four data. One is the administrator's user name, the second is the administrator's login password, and the third is to select the matching User permissions, and finally the verification code pushed by the system is correctly entered into the edit box. During the login verification process, these four data must be consistent to pass the verification.

The administrator login interface is shown in Figure 16.