Scribd
Upload
1K views11 pages

Patient Information System

This document outlines the analysis and design of a patient information system. It includes use case diagrams, lists of actors and use cases, activity diagrams and class diagrams for key functions like adding, updating and searching for patient information. The system analysis covers user login/logout, managing patient, doctor and facility information, and tracking patient history and examinations. The design section will cover data modeling and interfaces.

Uploaded by

xuanphong.nguyen
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views11 pages

Patient Information System

This document outlines the analysis and design of a patient information system. It includes use case diagrams, lists of actors and use cases, activity diagrams and class diagrams for key functions like adding, updating and searching for patient information. The system analysis covers user login/logout, managing patient, doctor and facility information, and tracking patient history and examinations. The design section will cover data modeling and interfaces.

Uploaded by

xuanphong.nguyen
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 11

Design Plan: Document Name: SWD/Form No.

Patient Information System Analysis and Design


Document
Effective Date: 12/22/2006 Version 1.0 Page 1 of 11

Patient Information System

Part 1. Introduce
Part 2. System Analysis
2.1. Use case diagram

2.2. List of actors

2.3. List of use cases

2.4. Specifying use cases


2.4.1. Use case login
2.4.2. Use case logout
2.4.3. Use case patient’s information management
2.4.4. Use case search a existent patient
2.4.5. Use case patient’s history
2.4.6. Use case patient’s health examination
2.4.7. Use case management of patient’s bed changes
2.4.8. Use case doctor’s information management
2.4.9. Use case search a existent doctor
2.4.10. Use case bed management
2.4.11. Use case search a available bed
2.4.12. Use case room management
2.4.13. Use case department management
2.4.14. Use case treatment management
2.4.15. Use case room type management
2.4.16. Use case status type management
2.4.17. Use case end user management
2.5. Activity Diagram
Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 2 of 11

2.5.1. Add a new patient

End user Patient Information System

End user choose function add a


new patient

System show a new form to input


patient’s information

End user input patient’s


information

End user choose function add


patient

System check inputted


information

[False]
If inputted information is legal

[True]

System save new patient’s


information to database
Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 3 of 11

2.5.2. Update a patient


Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 4 of 11

End user Patient Information System

End user choose a patient to


update his information

End user choose function


update a patient

System will get chosen patient’s


information and then show a new
form to update patient’s
information

End user change patient’s


information

End user choose function


update patient

System check inputted


information

[False]
If inputted information is legal

[True]

System update new patient’s


information to database
Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 5 of 11

2.5.3. Delete patients

End user Patient Information System

End user choose patients to


delete

End user choose function delete


these patients

System will check relative


information in other tables

If system contain relative [False]


information

[True]

System send a announcement


System delete patient’s
to end user – this patient can not
information in database
delete

2.5.4. Search patient


Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 6 of 11

End user Patient Information System

End user input keyword to find


out patient’s information

End user choose function search


patient

System search in database with


correlative keyword

If result has a patient a least


[False]

[True]

System send announcement is


System send result to end user
not find out patients

2.6. Class Diagrams


2.6.1. Add a new patient
Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 7 of 11

1 0..1
Patient Management Form Add Patient Form

Patient Controller

Patient

2.6.2. Update a patient

1 0..1
Patient Management Form Update Patient Form

Patient Controller

Patient

2.6.3. Delete patients


Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 8 of 11

1 1 1 1
Patient Management Form Patient Controller Patient

2.6.4. Search patient’s information

1 1 1 1
Patient Management Form Patient Controller Patient

2.7. Sequence Diagrams


2.7.1. Add a new patient

2.7.2. Update a patient


Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 9 of 11

2.7.3. Delete patients


Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 10 of 11

2.7.4. Search patient’s information


Design Plan: Document Name: SWD/Form No.
Patient Information System Analysis and Design
Document
Effective Date: 12/22/2006 Version 1.0 Page 11 of 11

Part 3. System Design


3.1. Data Design

3.2. Interface Design

You might also like