- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Patient Information System Activity Diagram
This is the Activity UML diagram of Patient Information System which shows the flows between the activity of Test, Patient, Appoitments, Treatment, Medicine. The main activity involved in this UML Activity Diagram of Patient Information System are as follows:
- Test Activity
- Patient Activity
- Appoitments Activity
- Treatment Activity
- Medicine Activity
Features of the Activity UML diagram of Patient Information System
- Admin User can search Test, view description of a selected Test, add Test, update Test and delete Test.
- Its shows the activity flow of editing, adding and updating of Patient
- User will be able to search and generate report of Appoitments, Treatment, Medicine
- All objects such as ( Test, Patient, Medicine) are interlinked
- Its shows the full description and flow of Test, Treatment, Medicine, Appoitments, Patient
Login Activity Diagram of Patient Information System:
This is the Login Activity Diagram of Patient Information System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Appoitments, Test, Patient, Medicine, Treatment. All the pages such as Patient, Medicine, Treatment are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Patient Information System. The various objects in the Medicine, Appoitments, Test, Patient, and Treatment page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Patient Information System Class Diagram
Patient Information System Class Diagram describes the structure of a Patient Information System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Patient Information System are Tests, Treatments, Reports, Doctors, Patient, Medicines.
Classes of Patient Information System Class Diagram:
- Tests Class : Manage all the operations of Tests
- Treatments Class : Manage all the operations of Treatments
- Reports Class : Manage all the operations of Reports
- Doctors Class : Manage all the operations of Doctors
- Patient Class : Manage all the operations of Patient
- Medicines Class : Manage all the operations of Medicines
Classes and their attributes of Patient Information System Class Diagram:
- Tests Attributes : test_id, test_patient_id, test_name, test_type, test_cost, test_report, test_description
- Treatments Attributes : treatment_id, treatment_name, treatment_type, treatment_description
- Reports Attributes : report_id, report_title, report_type, report_description
- Doctors Attributes : doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
- Patient Attributes : patient_id, patient_name, patient_mobile, patient_email, patient_username, patient_password, patient_address,
- Medicines Attributes : medicine_id, medicine_name, medicine_company, medicine_composition, medicine_cost, medicine_type, medicine_dose, medicine_description
Classes and their methods of Patient Information System Class Diagram:
- Tests Methods : addTests(), editTests(), deleteTests(), updateTests(), saveTests(), searchTests()
- Treatments Methods : addTreatments(), editTreatments(), deleteTreatments(), updateTreatments(), saveTreatments(), searchTreatments()
- Reports Methods : addReports(), editReports(), deleteReports(), updateReports(), saveReports(), searchReports()
- Doctors Methods : addDoctors(), editDoctors(), deleteDoctors(), updateDoctors(), saveDoctors(), searchDoctors()
- Patient Methods : addPatient(), editPatient(), deletePatient(), updatePatient(), savePatient(), searchPatient()
- Medicines Methods : addMedicines(), editMedicines(), deleteMedicines(), updateMedicines(), saveMedicines(), searchMedicines()
Class Diagram of Patient Information System :
- Posted By: freeproject
- Comments: 0
Patient Information System Component Diagram
This is a Component diagram of Patient Information System which shows components, provided and required interfaces, ports, and relationships between the Appoitments, Patient, Test, Treatment and Doctors. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Patient Information System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Patient Information System:
- Appoitments Component
- Patient Component
- Test Component
- Treatment Component
- Doctors Component
Featues of Patient Information System Component Diagram:
- You can show the models the components of Patient Information System.
- Model the database schema of Patient Information System
- Model the executables of an application of Patient Information System
- Model the system's source code of Patient Information System
- Posted By: freeproject
- Comments: 0
Patient Information System Dataflow Diagram
Patient Information System Data flow diagram is often used as a preliminary step to create an overview of the Patient Information without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Patient Information process. It contains all of the userflow and their entities such all the flow of Patient, Doctor, Appointment, Booking, Medicine, Test, Doctor Shedule. All of the below diagrams has been used for the visualization of data processing and structured design of the Patient Information process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Patient Information System :
This is the Zero Level DFD of Patient Information System, where we have eloborated the high level process of Patient Information. It’s a basic overview of the whole Patient Information System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Medicine,Test and Doctor Shedule showing the system as a single high-level process, with its relationship to external entities of Patient,Doctor and Appointment. It should be easily understood by a wide audience, including Patient,Appointment and Medicine In zero leve DFD of Patient Information System, we have described the high level flow of the Patient Information system.High Level Entities and proccess flow of Patient Information System:
- Managing all the Patient
- Managing all the Doctor
- Managing all the Appointment
- Managing all the Booking
- Managing all the Medicine
- Managing all the Test
- Managing all the Doctor Shedule
First Level Data flow Diagram(1st Level DFD) of Patient Information System :
First Level DFD (1st Level) of Patient Information System shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the Patient Information System system as a whole. It also identifies internal data stores of Doctor Shedule, Test, Medicine, Booking, Appointment that must be present in order for the Patient Information system to do its job, and shows the flow of data between the various parts of Patient, Appointment, Test, Doctor Shedule, Medicine of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of Patient Information.Main entities and output of First Level DFD (1st Level DFD):
- Processing Patient records and generate report of all Patient
- Processing Doctor records and generate report of all Doctor
- Processing Appointment records and generate report of all Appointment
- Processing Booking records and generate report of all Booking
- Processing Medicine records and generate report of all Medicine
- Processing Test records and generate report of all Test
- Processing Doctor Shedule records and generate report of all Doctor Shedule
Second Level Data flow Diagram(2nd Level DFD) of Patient Information System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Patient Information. It may require more functionalities of Patient Information to reach the necessary level of detail about the Patient Information functioning. First Level DFD (1st Level) of Patient Information System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Doctor Shedule, Test, Medicine, Booking, Appointment, Doctor, Patient.Low level functionalities of Patient Information System
- Admin logins to the system and manage all the functionalities of Patient Information System
- Admin can add, edit, delete and view the records of Patient, Appointment, Medicine, Doctor Shedule
- Admin can manage all the details of Doctor, Booking, Test
- Admin can also generate reports of Patient, Doctor, Appointment, Booking, Medicine, Test
- Admin can search the details of Doctor, Medicine, Test
- Admin can apply different level of filters on report of Patient, Booking, Medicine
- Admin can tracks the detailed information of Doctor, Appointment, Booking, , Medicine
- Posted By: freeproject
- Comments: 0
Patient Information System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Patient Information System Entity. The entity-relationship diagram of Patient Information System shows all the visual instrument of database tables and the relations between Treatments, Doctors, Tests, Medicines etc. It used structure data and to define the relationships between structured data groups of Patient Information System functionalities. The main entities of the Patient Information System are Tests, Treatments, Reports, Doctors, Patient and Medicines.
Patient Information System entities and their attributes :
- Tests Entity : Attributes of Tests are test_id, test_patient_id, test_name, test_type, test_cost, test_report, test_description
- Treatments Entity : Attributes of Treatments are treatment_id, treatment_name, treatment_type, treatment_description
- Reports Entity : Attributes of Reports are report_id, report_title, report_type, report_description
- Doctors Entity : Attributes of Doctors are doctor_id, doctor_name, doctor_specialist, doctor_mobile, doctor_email, doctor_username, doctor_password, doctor_address
- Patient Entity : Attributes of Patient are patient_id, patient_name, patient_mobile, patient_email, patient_username, patient_password, patient_address,
- Medicines Entity : Attributes of Medicines are medicine_id, medicine_name, medicine_company, medicine_composition, medicine_cost, medicine_type, medicine_dose, medicine_description
Description of Patient Information System Database :
- The details of Tests is store into the Tests tables respective with all tables
- Each entity ( Medicines, Reports, Patient, Treatments, Tests) contains primary key and unique keys.
- The entity Reports, Patient has binded with Tests, Treatments entities with foreign key
- There is one-to-one and one-to-many relationships available between Patient, Doctors, Medicines, Tests
- All the entities Tests, Patient, Reports, Medicines are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Patient Information System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Patient Information System Sequence Diagram
This is the UML sequence diagram of Patient Information System which shows the interaction between the objects of Treatment, Appoitments, Medicine, Patient, Doctors. The instance of class objects involved in this UML Sequence Diagram of Patient Information System are as follows:
- Treatment Object
- Appoitments Object
- Medicine Object
- Patient Object
- Doctors Object
Login Sequence Diagram of Patient Information System:
This is the Login Sequence Diagram of Patient Information System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Medicine, Treatment, Appoitments, Doctors, Patient. All the pages such as Appoitments, Doctors, Patient are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Patient Information System. The various objects in the Doctors, Medicine, Treatment, Appoitments, and Patient page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Patient Information System which shows the interaction between the objects of Treatment, Appoitments, Medicine, Patient, Doctors. The instance of class objects involved in this UML Sequence Diagram of Patient Information System are as follows:
- Treatment Object
- Appoitments Object
- Medicine Object
- Patient Object
- Doctors Object
- Posted By: freeproject
- Comments: 0
Patient Information System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Patient Information System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Patient Information System. The main actors of Patient Information System in this Use Case Diagram are: Super Admin, System User, Doctors, Patients, who perform the different type of use cases such as Manage Tests, Manage Treatments, Manage Reports, Manage Doctors, Manage Patient, Manage Medicines, Manage Users and Full Patient Information System Operations. Major elements of the UML use case diagram of Patient Information System are shown on the picture below.
The relationships between and among the actors and the use cases of Patient Information System:
- Super Admin Entity : Use cases of Super Admin are Manage Tests, Manage Treatments, Manage Reports, Manage Doctors, Manage Patient, Manage Medicines, Manage Users and Full Patient Information System Operations
- System User Entity : Use cases of System User are Manage Tests, Manage Treatments, Manage Reports, Manage Doctors, Manage Patient, Manage Medicines
- Doctors Entity : Use cases of Doctors are Add Patients Informations, Add Patient Treatments, Add Medicines, Add Tests
- Patients Entity : Use cases of Patients are View Treatment Plans, View Medicines Routines, View Test Reports, View Prescriptions
Use Case Diagram of Patient Information System :
