当前位置：网站首页>Design and implementation of community hospital information system

The community hospital information system in this paper can solve the problem of low efficiency of medical management in community hospitals . The main development language of this system is Java, choose VUE Technology as the front-end framework ,SpringBoot For the back-end framework ,MySQL Responsible for data management , The front and back ends are separated . And a more comprehensive analysis of the whole system , The main analysis includes ： System requirements analysis , System function analysis , System design analysis and system test analysis . From the construction of development environment to technology selection 、 Design objectives 、 System process to system function , Have carried out detailed planning . The system development principle is modular design principle , Develop functional modules for community hospitals according to actual needs . This system It is divided into four modules ： Doctor module 、 Nurse module 、 Drug administrator module 、 System administrator module . The modular design facilitates the iterative upgrading of subsequent systems . The system has an elegant and concise user interface , Fast and easy-to-use system functions , It has certain practical value for community hospitals .

The emergence of community hospital information system can help community hospitals realize medical management informatization , Assist hospital staff to improve the efficiency of medical management of patients , The patient's satisfaction with seeing a doctor has also increased .

key word ： Community hospitals VUE technology MySQL database SpringBoot technology

ABSTRACT

With the advent of the information technology era, Internet information has become a must for all walks of life. With the continuous popularization of community hospitals in China, the past paper-based handwriting management method has lagged behind the times.

The information platform of community hospital in this paper can solve the problem of low efficiency of community hospital management. The main development language of this system is Java, and VUE framework technology is used as the front-end framework, springboot is the back-end framework, MySQL is responsible for data management. And the whole system is analyzed comprehensively, including: system demand analysis, system function analysis, system design analysis and system test analysis. From the construction of development environment to technology selection, system design objectives, system process to system functions, the development principle of this system is modular design principle, and functional modules for community hospitals are developed according to actual needs. The system is divided into four modules: Doctor module, nurse module, drug administrator module and system administrator module. The modular application provides convenience for the subsequent system iterative upgrade. The system has elegant and simple user interface, quick and easy to use system functions, and has sufficient practical value.

The emergence of community hospital information platform can help community hospitals realize information, help hospital staff improve the efficiency of medical management for patients, and the satisfaction of patients themselves is also improved accordingly.

Keywords: Community hospital VUE technology MySQL database SpringBoot technology

The introduction

1.1 The research background of this project is

In the rapid development of the Internet today , The popularization of network information technology makes information platform possible , Informatization reform has become the focus of all walks of life ......

For the management of community hospital information , Patient information , Patient diagnostic information , Hospital drug management , Different kinds of data are numerous after a long time of accumulation .....

After visiting and investigating hospitals in various communities , It is found that most of them still use paper slip signature and other means to record the diagnosis of patients and transmit information between doctors and nurses . In recent years, the state has continuously issued relevant policies to increase the development of community hospitals , The number of community hospitals is also increasing ......

be based on Java The community hospital information system developed by technology can bring a lot of convenience to the management of community hospital information , It saves invalid internal waste time between staff .......

1.2 Research status

For developed countries , The vast majority of community hospitals are already information-based management , Take the United States as an example 2010 The Obama administration promulgated 500 Billion dollars of medical ......

At present, the informatization level of community hospitals in China is not high , In some small-scale community hospitals in some areas, there is still the use of traditional paper for information management ......

With the Internet and Science ....

1.3 Development purpose

The purpose of the development of community hospital information system is to make the community hospital change from the previous traditional paper information management mode to information-based electronic management . Traditional paper tube .........

The use of community hospital information system has the following significance ：

The management and diagnosis of patient information by community hospital staff become convenient and fast .
Doctors can ......

1.4 Design objectives

Through learning on the network platform and in the Library 、 School's inquiry of literature , First, learn and master the necessary knowledge points of designing this system , Then start all .......

At the beginning of development, the system has carried out detailed technical selection , Finally decided to use VUE technology ,SpringBoot Technology is supplemented by MySQL Database construction I ......

In software engineering, the system must have a clear design goal at the beginning of design . Community hospital information system also has important design goals, including the following ：

（1） Conciseness ： After simple guidance, users can start to use .

（2） Applicability .........

2 Related technology

2.1 SpringBoot technology

2.1.1 SpringBoot brief introduction

SpringBoot The framework is currently ava The most popular development framework in the language ,SpringBoot stay Spring Optimize on the original basis , In the reserved Spring The original ........

Here are MVC The classic three-tier architecture and its role ：

1.view layer ： Mainly responsible for the communication with users .......... Some requests , Subsequent implementation classes will continue to call dao Layer to achieve the purpose of data processing .

3.dao layer ：dao The layer is mainly responsible for the connection with the database ........

MVC The main function hierarchy of is shown in the figure 2-1 Shown .

chart 2-1 MVC Hierarchical chart

2.1.2 SpringBoot advantage

（1） Cross platform . As early as Java At the beginning of language design ,SUN The goal of the company is to realize the advanced feature of cross platform , To achieve this goal SUN company .....

（2） High development efficiency .SpringBoot The most remarkable feature of is out of the box , Use modern IDE such as IntelliJ IDEA After simple configuration, you can complete the box ......

（3） Perfect system monitoring . Use SpringBoot The system developed by technology can be used SpringBoot Its own monitoring ability to control the operation of the system .....

（4） Extensibility is strong .SpringBoot Strict meaning ......

2.2 VUE technology

VUE As one of the most popular frameworks of front-end technology in China , Its design concept is different from the traditional JSP It is obviously different from other front-end frameworks , Its .....

2.3 Fore and aft end separation

As the most popular development method of Internet development, front end and back-end separation has many advantages in comparison with traditional development methods . The most important one is ......

（1） Highly decoupled ： After the front-end and back-end separation, the front-end and back-end personnel only focus on their own business development , Front and back end developers pass .......

2.4 MySQL database

MySQL As a famous .....

2.5 MyBatis-Plus

MyBatis-Plus It's in the original MyBatis The persistence layer framework developed again based on the framework , Responsible for the interaction with the database , It is characterized by MyBatis Original base ........

3 Systems analysis

The demand analysis of this system is mainly to study the target users of community hospital information system by consulting data and investigating , Familiar with community hospital information system .....

3.1 Feasibility analysis

This chapter analyzes and studies the system objectives to be achieved by the community hospital information system , Summarize a solution and demonstrate . The main analysis scheme is .......

3.1.1 Technical feasibility

Analyze whether the current technology is feasible according to the system purpose of the community hospital information system , This mainly includes the analysis of development resources , Develop resource analysis .....

（1） Software ： Adopt rapid iterative development ,SpringBoot Select as the main development framework of the back end ,VUE Select front-end frame , supplemented MySQ......

3.1.2 Economic feasibility

Analyze from all aspects of economy , First, at present, the network technology is developed, and the relevant information about the development of this system can be queried in major technology forums , second ,.....

3.2 Functional requirements analysis

The function of the community hospital information system is perfect 、 It's easy to operate 、 clear screen , The system is mainly composed of four functional modules , Each is a doctor module , guard .....

3.2.1 Doctor function module

There is patient list management in the doctor function module 、 Patient examination 、 Four functions of patient diagnosis and personal data .

（1） Patient list function ： You can view the list of patients and enter the new patient information .

（2） Check the management function ......

The use case diagram of doctor function module is shown in Figure 3-1 Shown .

chart 3-1 Doctor function module use case diagram

3.2.2 Nurse function module

The nurse function module includes examination management and infusion management , Three functions of personal data .

（1） Patient check function ： The medical ....

（3） Personal center function ： Nurses can fix .....

chart 3-2 Nurse function module use case diagram

3.2.3 Drug administrator function module

The drug administrator function module includes taking drugs 、 Settlement and personal data .

（1） Drug taking function ： After the doctor has diagnosed the patient , After the doctor prescribes medicine for the patient , The drug administrator is responsible for assisting patients in taking drugs .

（2） Settlement function ： In patients with ........

chart 3-3 Drug administrator function module use case diagram

3.2.4 System administrator function module

（1） Account management function ： For each hospital .....

（2） Personal center function ： The system administrator can modify personal information , You need to operate in the personal center module .

The system administrator function module is shown in the figure 3-4 Shown .

chart 3-4 System administrator module use case diagram

3.3 Non functional requirements analysis

Non functional requirements also play an important role in the comprehensive application of the system , Non functional .....

（1） System performance requirements ： Systematic ....

（2） System usability requirements ： System ........

3.3.1 Operating environment requirements

operating system ： Windwos10

processor ： i3-6100 And above

Memory ： 4G

browser ： Google Chrome

database ： MySQL 8.0

3.4 System design principles

A relatively complete system design can be obtained by summarizing a number of system analysis results before this paper , Follow excellent and good system design [3] Developed system

In the design of this system , This system can meet the following two requirements ：

（1） Suitability ： System .........

4 The system design

4.1 System structure design

After the functional requirements analysis in the third chapter , We can get the functional structure diagram of the community hospital information system , Pictured 4-1 Shown .

chart 4-1 System function structure diagram

4.3 System flow design

At the stage of system process design, it is necessary to clearly understand every operation process of the system , Master all operation related contents of the system, including information ......

The workflow of community hospital information system is roughly ： Run the system and enter the main interface of the system , Select the user type . After logging in, users of doctor type can .......

You can log in with different identities when entering the system , The login process is shown in the figure 4-2 Shown .

chart 4-2 Login flowchart

Doctor users can add information to the patient list 、 Delete 、 Change 、 Check operation , Add the information flow chart as 4-3 Shown .

chart 4-3 Doctors add patient flow charts

Doctor users examine patients , The nurse went to carry out the examination order issued by the doctor , The doctor will issue diagnostic information for the patient after checking the examination results . The flow chart of doctors' diagnosis for patients is shown in Figure 4-4 Shown .

chart 4-4 Flow chart of doctor diagnosing patients

After the doctor arranges the examination for the patient , The nurse is responsible for carrying out the examination of the patient , Its flow chart is shown in 4-5 Shown .

chart 4-5 The nurse checks the flow chart for the patient

After the doctor diagnosed the patient , The drug administrator is responsible for assisting patients in taking drugs , Its flow chart is shown in 4-6 Shown .

chart 4-6 The drug administrator takes the drug flow chart for the patient

The system administrator is fully responsible for the management of system users , Its flow chart is shown in 4-7 Shown .

chart 4-7 System administrator manages user flow chart

4.4 System database design

Database is an important role in the system , The database bears the function of carrying all data in the system . The excellent database with detailed design can provide ......

4.4.1 database Conceptual structural design

Database E-R Graph is an important means to establish the concept of database , Under design ........

chart 4-8 System as a whole E-R chart

The third chapter of this paper has divided the functional modules of the system , According to the corresponding division conclusion, the entities required by this system can be analyzed , The main entity diagram of this system is as follows ：

（1） The attribute diagram of doctor entity is shown in the figure 4-9 Shown .

chart 4-9 Doctor entity attribute diagram

（2） The attribute diagram of nurse entity is shown in the figure 4-10 Shown .

chart 4-10 Doctor entity attribute diagram

（3） The attribute diagram of the system administrator entity is shown in the figure 4-11 Shown .

chart 4-11 System administrator entity attribute diagram

（4） The patient entity attribute diagram is shown in the figure 4-12 Shown .

chart 4-12 Patient entity attribute map

（5） The entity attribute diagram of the drug administrator is shown in the figure 4-13 Shown .

chart 4-13 Entity attribute diagram of drug administrator

4.4.2 database Logical structure design

The table structure design of database is generally determined according to the functional requirements of the system . The system is based on the database used MySQL database . This database is installed with ......

（1） Doctor Information Form ： Its primary key is number , The main fields include number , Name of doctor, etc . The detailed table structure design is shown in table 4-1 Shown .

surface 4-1 Doctor's watch

Field name	data type	length	Is it allowed to be empty	remarks
id	int	11	no	Number
Addtime	varchar	200	no	Add the time
Yishengbianhao	varchar	200	no	Doctor number
Mima	varchar	200	no	password
Yishengxingming	varchar	200	yes	Name of doctor
Xingbie	varchar	200	yes	Gender
Keshi	varchar	200	yes	department
Zhicheng	int	200	yes	The title
Shouji	varchar	200	yes	mailbox
Youxiang	varchar	200	yes	mailbox
Zhaopian	Varchar	200	yes	Photo URL
Shenfenzheng	Varchar	200	yes	Id card

（2） Patient information sheet ： Its primary key is number , The main fields include number , Patient name , Add the time , Patient name , Gender, etc . The detailed table structure design is shown in table 4-2 Shown .

surface 4-2 Patient table

Field name	data type	length	Is it allowed to be empty	remarks
id	int	11	no	Number
Addtime	varchar	255	no	Add the time
Huanzhezhanghao	varchar	255	no	Patient number
Mima	varchar	255	no	password
Huanzhexingming	varchar	255	yes	Patient name
Xingbie	varchar	255	yes	Gender
Nianling	varchar	11	yes	Age
Shouji	int	11	yes	mobile phone
Youxiang	varchar	255	yes	mailbox
Shenfengzheng	varchar	255	yes	ID number
Zhaopian	int	11	yes	Photo URL

（3） Information form of drug administrator ： Its primary key is number , The main fields include number , Name of drug administrator , Add the time , full name , Gender, etc . The detailed table structure design is shown in table 4-3 Shown .

surface 4-3 Drug administrator table

Field name	data type	length	Is it allowed to be empty	remarks
id	int	11	no	Number
Addtime	Timestamp	0	no	Add the time
Huanzhezhanghao	varchar	255	no	Number
Mima	varchar	255	no	password
Guanliyuanxingming	varchar	255	yes	full name
Xingbie	varchar	255	yes	Gender
Shouji	int	11	yes	mobile phone
Youxiang	varchar	255	yes	mailbox
Touxiang	Varchar	200	yes	Photo URL

（4） List of information to be checked ： Its primary key is number , The main fields include number , Add the time , Patient number , Patient name 、 full name , Gender, etc . The detailed table structure design is shown in table 4-4 Shown .

surface 4-4 Checklist to be checked

Field name	data type	length	Is it allowed to be empty	remarks
id	int	11	no	Number
Addtime	Timestamp	0	no	Add the time
Huanzhezhanghao	varchar	255	no	Patient number
Mima	varchar	255	no	password
Guanliyuanxingming	varchar	255	yes	Patient name
Xingbie	varchar	255	yes	Gender
Shouji	int	11	yes	mobile phone
Youxiang	varchar	255	yes	mailbox
Touxiang	Varchar	200	yes	Photo URL

（5） System administrator information table ： Its primary key is number , The main fields include number , Add the time , Patient number , Patient name 、 Gender, etc . The detailed table structure design is shown in table 4-5 Shown .

surface 4-5 Administrator information table

Field name	data type	length	Is it allowed to be empty	remarks
id	int	11	no	Number
Username	Varchar	100	no	full name
Password	varchar	100	no	password
Role	varchar	100	no	role
Guanliyuanxingming	varchar	255	yes	Patient name

5 system implementation

5.1 The system login function is realized

When using the community hospital information system , Users need to log in , Select the user phase in the system login interface ......

chart 5-1 System login interface

5.2 Doctor module function realization

After the doctor successfully logs in , The system will jump to the corresponding system main interface of the doctor , The display diagram is shown in the figure 5-2 Shown .

chart 5-2 Doctor main interface

The main code is as follows ：

@RestController

@RequestMapping("/yisheng")

public class YishengController {

@Autowired

private YishengService yishengService;

@Autowired

private TokenService tokenService;

/**

* Sign in

@IgnoreAuth

@RequestMapping(value = "/login")

public R login(String username, String password, String captcha, HttpServletRequest request) {

YishengEntity user = yishengService.selectOne(new EntityWrapper<YishengEntity>().eq("yishenggonghao", username));

if(user==null || !user.getMima().equals(password)) {

return R.error(" Incorrect account or password ");

}

String token = tokenService.generateToken(user.getId(), username,"yisheng", " Doctor " );

return R.ok().put("token", token);

}

（1） Patient management

There is a list of patients in the doctor user's menu , Personal center , Inspection result management , Diagnostic information management . Can be queried accordingly , add to , Delete , Modify the operating . Add patients as shown 5-3 Shown , Modify the patient information as shown in the figure 5-4 Shown , Delete the patient as shown in the figure 5-5 Shown .

chart 5-3 Add patient information

chart 5-4 Modify patient information

chart 5-5 Delete patient information

（2） Inspection management

After the doctor user adds patient information, the patient can be checked to provide information for diagnosis , Enter the corresponding examination content after the doctor clicks arrange examination , The nurse can query the corresponding content to check the patient, as shown in the figure 5-6 Shown .

chart 5-6 The doctor arranges an examination

（3） Diagnosis management

After the nurse has diagnosed the patient , Doctors can inquire about the examination of patients , Then you can diagnose the patient with the diagnostic information , The diagnosis interface is shown in the figure 5-7 Shown .

chart 5-7 The doctor makes a diagnosis

5.3 Nurse module function realization

Nurse type users log in to the system , Will directly enter the nurse main interface , Including personal Center , Patient management , To be checked list management , Inspection result management , Injection list management , Complete injection list management . The interface is shown in the figure 5-8 Shown .

chart 5-8 Nurse main interface

The nurse can query the patients to be examined in the menu of the list to be examined , The interface to be checked is shown in the figure 5-7 Shown . The interface when the nurse checks the patient , Pictured 5-9 Shown .

chart 5-8 Interface to be checked

The main codes are as follows ：

/**

* Back end details

@RequestMapping("/info/{id}")

public R info(@PathVariable("id") Long id){

HushiEntity hushi = hushiService.selectById(id);

return R.ok().put("data", hushi);

}

/**

* Front end details

@RequestMapping("/detail/{id}")

public R detail(@PathVariable("id") Long id){

HushiEntity hushi = hushiService.selectById(id);

return R.ok().put("data", hushi);

}

/**

* Back end save

@RequestMapping("/save")

public R save(@RequestBody HushiEntity hushi, HttpServletRequest request){

hushi.setId(new Date().getTime()+new Double(Math.floor(Math.random()*1000)).longValue());

hushi.setId(new Date().getTime());

hushiService.insert(hushi);

return R.ok();

}

chart 5-9 Nurse examination interface

The main code is as follows ：

/* Nurse related operations */

@RequestMapping("/remind/{columnName}/{type}")

public R remindCount(@PathVariable("columnName") String columnName, HttpServletRequest request,

@PathVariable("type") String type,@RequestParam Map<String, Object> map) {

map.put("column", columnName);

map.put("type", type);

Wrapper<HushiEntity> wrapper = new EntityWrapper<HushiEntity>();

if(map.get("remindstart")!=null) {

wrapper.ge(columnName, map.get("remindstart"));

}

if(map.get("remindend")!=null) {

wrapper.le(columnName, map.get("remindend"));

}

int count = hushiService.selectCount(wrapper);

return R.ok().put("count", count);

}

5.4 The function realization of the drug administrator module

Users of the drug administrator type log in to the system , It will directly enter the main interface of drug administrator , Including personal Center , Diagnostic information management 、 Take medicine list management 、 There are two operation menus for drug fee settlement management and drug information management , The interface is shown in the figure 5-10 Shown .

chart 5-10 Drug administrator interface

The main code is as follows ：

@RestController

@RequestMapping("/yaopinguanliyuan")

public class YaopinguanliyuanController {

@Autowired

private YaopinguanliyuanService yaopinguanliyuanService;

@Autowired

private TokenService tokenService;

/**

* Sign in

@IgnoreAuth

@RequestMapping(value = "/login")

public R login(String username, String password, String captcha, HttpServletRequest request) {

YaopinguanliyuanEntity user = yaopinguanliyuanService.selectOne(new EntityWrapper<YaopinguanliyuanEntity>().eq("guanliyuanzhanghao", username));

if(user==null || !user.getMima().equals(password)) {

return R.error(" Incorrect account or password ");

}

String token = tokenService.generateToken(user.getId(), username,"yaopinguanliyuan", " Drug Administrator " );

return R.ok().put("token", token);

}

（1） Take medicine list management

After the doctor diagnoses the patient, the doctor will prescribe medicine for the patient , At this time, the drug administrator should be responsible for assisting the patient in taking medicine , Pictured 5-11 Shown .

chart 5-11 The drug administrator takes the drug interface

（2） Settlement management

After the patient takes the medicine , The drug administrator helps the patient with the settlement , Pictured 5-12 Shown .

chart 5-12 Drug administrator settlement interface

The main code is as follows ：

/**

* modify

@RequestMapping("/update")

public R update(@RequestBody YaopinguanliyuanEntity yaopinguanliyuan, HttpServletRequest request){

//ValidatorUtils.validateEntity(yaopinguanliyuan);

yaopinguanliyuanService.updateById(yaopinguanliyuan);// All updates

return R.ok();

}

/**

* Delete

@RequestMapping("/delete")

public R delete(@RequestBody Long[] ids){

yaopinguanliyuanService.deleteBatchIds(Arrays.asList(ids));

return R.ok();

}

5.5 System administrator function implementation

Users of the system administrator type can log in successfully after entering the correct account and password , It will directly jump to the system administrator main interface , Functions include personal Center , Patient management , Nurse management , Doctor management , The drug administrator manages five operation menus , The interface is shown in the figure 5-13 Shown .

chart 5-13 System administrator main interface

The main code is as follows ：

@Autowired

private UserService userService;

@Autowired

private TokenService tokenService;

/**

* Sign in

@IgnoreAuth

@PostMapping(value = "/login")

public R login(String username, String password, String captcha, HttpServletRequest request) {

UserEntity user = userService.selectOne(new EntityWrapper<UserEntity>().eq("username", username));

if(user==null || !user.getPassword().equals(password)) {

return R.error(" Incorrect account or password ");

}

String token = tokenService.generateToken(user.getId(),username, "users", user.getRole());

return R.ok().put("token", token);

}

User management

The system administrator has the function of managing other user information of the system . The nurse information interface is shown in the figure 5-14 Shown .

chart 5-14 Nurse information interface

The main code is as follows ：

/**

* Paging list

@RequestMapping("/page")

public R page(@RequestParam Map<String, Object> params,UserEntity user){

EntityWrapper<UserEntity> ew = new EntityWrapper<UserEntity>();

PageUtils page = userService.queryPage(params, MPUtil.sort(MPUtil.between(MPUtil.allLike(ew, user), params), params));

return R.ok().put("data", page);

}

/**

* Non paged list

@RequestMapping("/list")

public R list( UserEntity user){

EntityWrapper<UserEntity> ew = new EntityWrapper<UserEntity>();

return R.ok().put("data", userService.selectListView(ew));

}

6 The system test

After the system or software project is developed , All need to go through detailed tests before they can be delivered online , The purpose of bit system testing is to find out what appears in the development process but does not ........

6.1 A functional test

There are five tests designed for this system , The test results are shown in the table 6-1 Shown .

surface 6-1 System function test

Test items	Test evaluation
Link correctness	normal
database	normal
Form data correctness	normal
stability	normal
Security	normal

6.2 Security testing

Security testing is to test the overall security of the system . The main safety tests of this system are as follows ：

（1） Log in to the platform to test . Before logging in and using this system, you should choose the correct corresponding identity , Then enter the correct user name and password , Any one of them is wrong , all ......

6.3 Performance testing

Performance testing is a comprehensive and large-scale application of the developed system , Observe and record the indicators of the analysis system through secondary methods , This system mainly carries out .........

6.4 Usability testing

The design of usability test is mainly to test whether the use process and operation of the system are reasonable ........

surface 6-2 System availability test

Test items	Test evaluation
The window moves 、 Change in size 、 Whether closing and other operations are normal	yes
modular 、 Whether the prompt content and other text descriptions are correct	yes
Whether the module layout is coordinated 、 reasonable	yes
Whether to display prompt information after error operation	yes
mouse 、 Whether keyboard operation supports	yes
Whether the required data items are displayed correctly	yes
Whether the operation process is reasonable	yes

6.5 The test case

Make test cases for each function in this system .

6.5.1 User login test

surface 6-3 Log in to the test case table

Serial number	input data	Expected results	test result
1	Select the login type and enter the correct account number for the doctor , password .	Landing successful	Login successfully and enter the doctor main interface
2	Select the login type as or doctor, and enter the correct account number of the nurse , Password or verification code	Login failed	Login failure shows that the account or password is wrong
3	Select the login type and enter the correct account number for the doctor , Enter the wrong password	Login failed	Login failure shows password error
4	Select the login type and enter the correct account number for the nurse , Don't fill in the password	Login failed	Login failure shows that the password cannot be empty
5	Select the login type and enter the correct account number for the administrator , Enter the wrong password	Login failed	Login failure shows that the account or password is wrong
6	Select the login type and enter the correct password for the administrator , Do not enter account number	Login failed	Login failure shows that the account cannot be empty

6.5.2 Add patient tests

All core functions of this system are to ultimately serve patients , So add ......

surface 6-4 Add patient function test

Serial number	testing procedure	Expected results	test result
1	Paste directly in the browser to enter the doctor to add the patient URL	Add failure	System interception , Need to log in
2	Try adding a patient using the nurse account	Add failure	The nurse interface only has permission to view patients
3	Use the doctor account to add patients , Do not fill in the patient information	Add failure	The prompt message is incomplete , Unable to add
4	Log in with a doctor's account , Fill in the patient information correctly	Add success	Successfully added patient

6.5.3 Patient examination test

Patients after adding , When the doctor needs the patient to be examined, the doctor ......

surface 6-5 Patient check function test form

Serial number	testing procedure	Expected results	test result
1	After the doctor logs in, select the patient examination in the patient list , And enter the inspection type	Add success	success
2	After the nurse logs in, check the checklist	The query is successful	You can check the examination arranged by the doctor
3	The nurse is performing an examination , Record the inspection results	Add success	success
4	The doctor queries the patient's examination results in the examination results	The query is successful	Successful query of patient examination results
5	The doctor diagnosed the patient in the examination results	Add success	Successfully added diagnostic record

6.5.4 Drug administrator function test

The core function of the drug administrator is to assist patients in taking drugs and settling accounts , The specific test results are shown in table 6-6 Shown ：

surface 6-6 Drug administrator's drug taking function test

Serial number	testing procedure	Expected results	test result
1	After logging in, the drug administrator enters the diagnostic information to query the diagnostic information issued by the doctor for the patient	success	success
2	The drug administrator arranges the patient to take medicine in the diagnostic information	success	Successfully added diagnostic record
3	The drug administrator settles the drug expenses for the patients who take the drugs	success	success

6.5.5 System administrator function test

The system administrator is mainly responsible for adding, deleting, modifying and querying users in the system , The specific test results are shown in table 6-7 Shown ：

surface 6-7 System administrator manages user function test

Serial number	testing procedure	Expected results	test result
1	System administrator views patient list , And add , Delete , Modify the operating	success	All patients were successfully queried , And successfully added 、 Delete 、 Modify patient information
2	The system administrator views the list of doctors , And add , Delete , Modify the operating	success	All doctors were successfully queried , And successfully added 、 Delete 、 Modify doctor information
3	The system administrator views the nurse list , And add , Delete , Modify the operating	success	All nurses were successfully queried , And successfully added 、 Delete 、 Modify nurse information
4	The system administrator views the list of drug administrators , And add , Delete , Modify the operating	success	All drug administrators were successfully queried , And successfully added 、 Delete 、 Modify the information

6.6 Test conclusion

The community hospital information system has basically met the previous system functional requirements , system .....

6.7 System improvement objectives

（1） Improve the security of the whole database and system , Make the security of the system like those mature ......

7 Summary and prospect

7.1 summary

All functions of the community hospital information system can be realized , Achieved the desired effect . Through the development of this system , Use more skillfully MySQL, Front end and back end separation architecture ,VU.....

（1） By consulting the relevant literature about community hospital informatization , Summarize the development status of community hospital information system . Through visiting and investigating several different community hospitals ......

（2） According to the actual visit .....

（3） The community hospital information system has basically achieved the expected goal of development , Each expected functional structure has been realized , This system enables doctors in community hospitals to enter .....

（4） After the usability test of the system , Safety test and performance test , The performance of the community hospital information system has been ......

7.2 expectation

The design and implementation of community hospital information system involves many aspects of knowledge , There are many problems and expansibility in this system , Further work is needed in the following aspects .....

If you need more information, please download it from the link below

Design and implementation of community hospital information system .rar- Internet document resources -CSDN download The content includes detailed design documents word edition , Attached with opening report and related PPT Other documents , For your reference . You can also find more download resources on the home page of this blog 、 For learning materials, please visit CSDN Download channel .https://download.csdn.net/download/u013253075/47811792?spm=1001.2014.3001.5503

原网站

版权声明
本文为[Salted fish brother]所创，转载请带上原文链接，感谢
https://yzsam.com/2022/02/202202140915058863.html