Project Title: CLINICAL INFORMATION MANAGEMENT SYSTEM

Names of project developer

1. Assmamaw Damte
2. Kasahun Ybeltal

WACHEMO UNIVERSITY

College of Engineering and Technology

Department of Software Engineering

Submitted to: MESSAY ASCHALEW

20 September 2022

HOSANNA, ETHIOPIA

1
Table of Contents
1.1 Introduction.....................................................................................................................................2
1.2 Background......................................................................................................................................3
1.3 Organizational Structure..................................................................................................................3
1.4 Literature Review............................................................................................................................4
1.5 Statement of the Problem...............................................................................................................5
1.6 Objective of the project...................................................................................................................5
1.6.1 General Objective.....................................................................................................................5
1.6.2 Specific Objective......................................................................................................................6
1.7. Feasibility of the Project.................................................................................................................6
1.7.1 Technical Feasibility..................................................................................................................6
1.7.2 Operational Feasibility..............................................................................................................6
1.7.3 Economical Feasibility...............................................................................................................6
1.7.3.1 Tangible.............................................................................................................................7
1.7.3.2 Intangible...........................................................................................................................7
1.8. Scope and Limitation......................................................................................................................7
1.9 Methodology of the Project.............................................................................................................7
1.9.1 Software Requirement Engineering Process Model..................................................................8
1.9.2 Software Analysis and Design Method.....................................................................................9
1.9.3 Requirement collection methods.............................................................................................9
1.9.4 Testing Method.......................................................................................................................10
1.9.5 Coding method.......................................................................................................................11
1.10 Significance of the project...........................................................................................................11
1.11 Team Composition of the project................................................................................................12
1.12 Project Schedule and Budget.......................................................................................................12
2 Chapter Two…………………………………………………………………………………………………………………………………15

2.1Introduction of existing system …………………………………………………………………………………………………15

2.2 Major functionality of existing system………………………………………………………………………………………15

2.3Document used in Existing System…………………………………………………………………………………………….15

2.4 users of the existing system ………………………………………………………………………..……………………………22

2.5 drawback of the existing system…………………………………………………….……………………………..………….22

2.6 Business rules of the domain…………………………………………………………….………………………………….…..22

2
2.7 Alternative solution……………………………………………………………….……………………………………………23

3. PROPOSED SYSTEM……………………………………………………………………………………………………………………25
3.1Introduction……………………………………………………………………………………………………………………………25

3.2 Functional requirement………………………………………………………………………………….………………….… 25

3.3. Non- Functional requirement………………………………… ………… …………………..………………………………25

3.3.1. User interface………………………………………………………………………………….……………………………………26

3.3.2. Hardware consideration…………………………………………………………..…………………..………………………26

3.3.3. Software consideration…………………………………………………………..…………………………..……………….26

3.3.4. Performance consideration………………………………………………………..………………………………………...26

3.3.5. Reliability………………………………………………………………..……………………………………………..27
3.3.6. Error handling………………………………………………………………………………………………………..27

3.3.7. Security………………………………………………………………………………….….…………………………..27

3.4. SYSTEM MODEL………………………………………………………………………………………………………..27

3.4.1Scenarios ………………………………………………………………………………………………………………..27

3.4.2. Actor Identification………………………………………………………………………………………………..27

3.4.3 Use-Case Identification…………………………………………………………………………..……………………………..28

3.4.3. Use case model…………………………………………………………………………………………………………………..28

3
1.1 Introduction
The goal of this project idea is to answer the needs and problems that are seen in the information
management system .By determining its problem we can have the ideas on what should be the
features of the system. Tie existence of a good system, systematic and safe requires the
management organization to oversee all information management effectively.

Clinical Information Management System is equipped with the automated features. It will remind
each room about the patient information that reached on each room and it also support reminder
for the patient information search. The web based system which is implementing in clinical
information management system is suitable to be used for effective time utilization and store the
patient information on the system. For card room page, admin can access all records related to
patient information and related information in the user equipment to store and update if there are
any changes to the records.

1.2 Background
The Nigest Eline hospital is found at Hasaean town located in South Nation’s Nationalities and
Peoples Region at 232kms south of Addis Ababa, is capital city of Ethiopia. This hospital was
established in 1984 in order to serve the catchment population over 2.5 million in the zone and
nearby zones and districts. The name of the hospital was repeatedly changed because of various
political and social reasons. Initially it was known as “Gaud Mengistu Haile Mariam hospital” during
“Derg Regime” which was the name of the former president of Ethiopia. However, this name was
not stayed for prolonged years due to the down fall of the Derge regime in 1991. Therefore,
Mengistu Haile Hospital Changed to Kambata and Hadiya province Hospital. Due to another reason
at that time, again the second name of the Hospital changed for the second time to Hasaean
Hospital. Finally, in 2008 the Hospital got its current name (Nigist Eleni Mohammed Hospital) under
Hadiya zone administration after momentous discussion and debate of stake holders and concerned
bodies It provides preventive, curative and rehabilitative clinical services organized in four case
teams as outpatient, inpatient, emergency and critical care, maternal, child health and obstetrics
and operation theatre. The hospital also has 24 hours emergency and critical care services now.

1.3 Organizational Structure

4
 University president

Chief Executive Directory V.P

Acadmaic Quality assurance Auditing ,legal,anticorruption .ethics ,PH,HMIS

CARD Chief community service director CCSD

Dean,school of
Chief clinical
----------------- Director ------------ CG&QA Unit CABDD

IQEA Coordinator Dept of Internal Medicne Finance, budget, procurement

& asset

Out patient Coordinator

Reform coordinator
Dept of surgery Human resource management

Dept of obs /gyn Facility management (laundry ,cleaning

CBE Coordinator electrical ,transport
Liason ,Referal & Social
Dept of pediatrics

Research Coordinator
Radiology Security head

Pre-clinical coordinator Nursing and midwifery Inpatient coordinator

Procurement & property admin

Clerkship coordinatorOphthalmology
Emergency & critical care
Food service & Nutrition
coordinator
Dermatology
Pharmacy
Student service management
psychiatry ICT
Nursing
Library
Laboratory
OR manager
Midwifery ansthesia

Biomedical Engineering
Laboratory

Midwifery

Public health

Other

5
1.4 Literature Review
[1] .The Aditya hospital management system on this project the general
objective is to make web base Aditya Hospital management system for Aditya
hospital and the specific objectives are to design system architecture,
understand functional and non functional requirements, to fulfil patient
information for each room and to send the message to patient for queue.
based on the project ,student that write the document, use object oriented
analysis and design ,object oriented programing language to implement the
Aditya hospital information management system. researcher used php ,other
programming language and XAMP server to store the patient
information ,JavaScript to validate the html document for skeleton of website
page or foster website page, and used css to make the website more beautiful.
They used unit testing, Integration Testing and functional Testing, white box
testing and Black box Testing. The Requirement Collection methods Used by
recercher were questionnaire, Requirement Reuse and prototype.
The gap we see from this project is listed hear The developer manly focus on
prototype requirement collection method, so the additional requirement come
from stackholder is not listed on the functional requirement. The system does
not automatically generate SMS to notify the room the patient where to go.
The patient does not hosting based on age.

1.5 Statement of the Problem

Patient information send from one room to an other room, distribution ,search and information
management in this regard are routine processes carried out in various hospitals across Ethiopia.

It is a common place to observe that these routine processes are still preformed manually or are
minimally computerized even in nigist eleni mohammed Hospital. This manual approach to these
routine operations has a lot of problems associated with it Such as:-
 Patient information disappear from storage place

6
  Difficulty in retrieving patient information
 lack of good storage information system for patient
 It is a costly and time consuming
 Search patient information is much difficult

1.6 Objective of the project

1.6.1 General Objective
The general objective of this project is to design and develop web based Clinical
Information Management System for Nigest Eleni Mohamed Hospital

1.6.2 Specific Objective

To achieve the general objective of the project the following specific objective will use:

 Requirement elicitation
 Requirement analysis
 Requirement specification
 Requirement design
 Development
 Testing
 Deployment
 Maintenance

1.7 Feasibility of the Project

A feasibility study is simply an assessment of the practicality of a proposed project plan or method.

1.7.1 Technical Feasibility

Technical feasibility is the formal process of assessing whether the nigist eleni hospital is technically
possible to use the system

The new system has technologies like network infrastructure, hardware, software .Hospital know
buy 300 computer to manage the patient information and network infrastructure access to
download cloud software or for other purpose. The hospital administrator Sayed that we will buy
technical material to functional the new system.

7
1.7.2 Operational Feasibility
The team member have Qualifications for this system science the employee member practice for
computer knowledge for one week to implement all automated machine by WCU university
president support.

Nigist Eleni Hospital work 24 hours to become the beginner in order to perform all the activities with
machine ,therefore the stakeholder become more power full skill on computer knowelege.

1.7.3 Economical Feasibility

The new system will provide many benefits to the Nigist Eleni hospital, especially for doctor and card
room.

We will see the economic feasibility by dividing into two categories tangible and intangible.

1.7.3.1 Tangible
 System reduce paper cost for patient information registration
 There is no time wastage for search patient information
 data warehouse that allows for more direct targeting of promotional mailings could be said
to have a tangible benefit of reducing mailing costs by 300,000 per year.
 The system reduce the pen cost by 300,00 birr per year

1.7.3.2 Intangible
 Patient get satisfaction and freely get the clinical service without any computing
 High quality of patient information
 Nigist Eleni Hospital get brand equity

hine ,therefore the stakeholder become more power full skill on

computer knowelege.

1.7.3 Economical Feasibility

The new system will provide many benefits to the Nigist Eleni hospital, especially for doctor and card
room.

We will see the economic feasibility by dividing into two categories tangible and intangible.

1.7.3.1 Tangible
 System reduce paper cost for patient information registration
 There is no time wastage for search patient information
 data warehouse that allows for more direct targeting of promotional mailings could be said
to have a tangible benefit of reducing mailing costs by 300,000 per year.
 The system reduce the pen cost by 300,00 birr per year

8
1.7.3.2 Intangible
 Patient get satisfaction and freely get the clinical service without any computing
 High quality of patient information
 Nigist Eleni Hospital get brand equity

1.8. Scope and Limitation

1.8.1 Scope
The scope of the project are the following:

 Search patient
 View patient
 Send patient full information to the concerned party
 Send notification for patient
 View patient information
 Give notification when new patient is coming for each room

1.8.2 Limitation
The limitation of this project are the following:-

 The system does not include for emergency room

 The system does not include payment method either bank or CBE birr.
 The system does not work with other hospital
 The system does not accessible by patient

1.9 Methodology of the Project

1.9.1 Software Requirement Engineering Process Model
A software process model is an abstraction of the software development process. The models
specify the stages and order of a process. So, think of this as a representation of the order of
activities of the process and the sequence in which they are performed.

This is to provide guidance for controlling and coordinating the tasks to achieve the end product and
objectives as effectively as possible.

9
From the above software development process model we choice incremental process model
because incremental process model have the following purpose for our system:

 A process of software development where requirements are broken down into multiple
standalone modules of software development cycle
 It is flexible and less expensive to change requirements and scope
 Errors are easy to be identified

 This model is less costly compared to others

10
1.9.2 Software Analysis and Design Method
1.9.2.1 Object Oriented Analysis (OOA)

This phase enabled us to look at the problem domain and the aim of producing conceptual model of
the information existing in the area which we are analysing. During this phase we will model the
function of the system (use case modelling), find and identify the business object, organize the
object and identify the relationship between them and finally model the behaviour of the object.

1.9.2.1 Object Oriented Design (OOD)

We decide to use object-oriented system analysis and design methodology for the reason of the
method Simplicity, reusability, modifiability and better way to construct, manage and assemble
object.
During this phase we will refine (modify) the use case model to reflect the implementation
environment, model object interactions and behaviour’s that support the use case scenario, and
finally update object model to reflect the implementation environment. And also transforms the
conceptual model produced in object-oriented analysis to take account of the constraints needed to
our system, so that we used this phase to improve the use case model to reflect the implementation
environment.

1.9.3 Requirement collection methods

Is the practice of collecting the requirements of a system from patient, doctor, card room and other
stakeholders. We use different data gathering methods such as interview, observation and
document analysis in order to determine the information, which is used in the existing system and
very important to develop web based Clinical information management system for Nigist Eleni
Mohammed hospital.
1.9.3.1 Interview
We have gathered information by interviewing the card room who works in Nigist Eleni hospital
about the existing system. We have prepared some questions to ETAT room ,card room, doctors

11
who works at OPD and the person who works in tragiary room to get the necessary information
about the existing system about Current work flows, Problems facing and the like.
1.9.3.2 Observation
We went to the hospital and observed their daily activity as regards their current system
and they were manually recording the patient information and related patient information.
We observe the queue of patient for getting each service especially in the card room and
send patient information from room to room using man power.
We observe the systems weaknesses like it was vulnerable to errors ,search patient
information and time consuming.
1.9.3.3 Document Analysis
We have seen Forms and documents, which the existing system currently uses in Nigist Eleni
hospital, in order to know processes, rules, regulations and constraints in the existing system that
can be used to design the new system.

1.9.4 Testing Method

The test method is designed to analysis the logic used in the implementation of the clinical
information management system. The tests will allow us to ensure correct program flow,
and to determine the error-handling capability of the system.
1.9.4.1 Unit Testing
Unit testing is a level of software testing where individual modules or components of software are
tested. The purpose is to validate that each unit of the software performs as designed. A unit is the
smallest testable part of any software. It usually has one or a few inputs and usually a single output.
For example:
When we test patient information registration module if the field is empty, the system will display
the message like, please fill out the field.

1.9.4.2 Integration Testing

The Integration testing part of a testing methodology is the testing of the different
modules/components that have been successfully unit tested when integrated together to perform

12
specific tasks and activities. The objective is to take unit tested modules and builds program
structure. All the modules are combined and tested as a whole. The individual form is doing well so
the collection of unit testing become the system is working well.

1.9.4.3 System testing

System testing, also referred to as system-level tests or system-integration testing, is the process in which a
quality assurance (QA) team evaluates how the various components of an application interact together in the
full, integrated system or application.

1.9.5 Coding method

We use web based programming language to develop CIMS for Nigist Eline Mohamed Hospital

We will plan to use the following programming tools and developmental Environments for our
project

Programing language and tools Description

Html It used to create and structure sections, paragraphs,
and links using elements, tags, and attributes. 
Css  It is to provide Web developers with a standard way
to define, apply, and manage sets of style
characteristics. 
JavaScript JavaScript is used to validate data and develop
different message. We will use JavaScript to validate
our data which we use in html code.
Php Is used to develop dynamic website .we will use php
to create our dynamic website.
Mysql It is used to create a database of the project

1.10 Significance of the project

This study is designed to address clinical information management practice at
Nigst Eleni hospital. It will find out the main problem and factors that affect the
healthcare facilities in the provision of essential information and service in the
demand of the patients due to managing clinical information.

 To save time and resource needed

 It will provide reliable patient information store services
13
  It will reduce paper cost
 It will reduce man power
 Better patient treatments

1.11 Team Composition of the project

Name ID Email Role
Asmamaw Damte 1200015 [email protected] Requirement elicitation, proposal ,
Kasahun yibeltal 1201005 [email protected] programmer, designer ,tester,
analysist

1.12 Project Schedule and Budget

1.12.1 Schedule

Project time schedule

No Tasks 2014
May 12- May18-21 May22-26 May27-29 May 30- June5 June7
16 june4
1 Proposal
2 Req Elicitation
Req Analysis
System Design
Implementation
Testing
Documentation and
project submission

1.12.2 Budget plan

Budget Plan

no Material Quantity Price in Birr Spend

1 Desktop 2 Covered by Wcu

computer

2 Laptop 2 30,000 60,000

14
 3 flash 1 350 350

4 pen 3 15 45

4 Transportation 6 10 60

6 printing 100 3 300

7 MS word 2016 free

8 Visio 2016 free

Total Birr 60,755

CHAPTER TWO
2. DESCRIPTION OF THE EXISTING SYSTEM
2.1 Introduction of the existing system
This chapter we will deals with analyzing the general workflow of the existing system, structure of
the system and also dealing with what strength and weaknesses are there in the existing system, the
problem of the existing system and the alternative solution, Features of system that offers many
flexible and convenient features.
The current system of Nigist Eleni Hospital is manual system and Uses Partial Computerized system .
However this partial computerized system is work only for registration and search .
This leads loosing time and resource of the hospital .
Generally in this chapter we will see the major function, strength and weakness , document ,and
business rule of existing system are mentioned.

2.2 Major function of the existing system

The existing system has the following functions

15
 Check any patient in trajiary room:-any patient get the direction from this room to
which room go to after the registration or search.
 Patient Registrations:-whenever a new patient comes to the hospital, the recorder
registers the patient manually.
 Search the patient information:-when the patient registered before, the recorder
searches the patient information by medical record number.
 The doctor writes patient history on……………
 The doctor sends the patient to the laboratory, a CT scan, and X-ray for additional
checking.
 After the patient is checked, the final result in the laboratory, CT scan, X-ray the
employee who works in this room sends again the result to the doctor.
 Card room stores the patient information:-after the patient gets treatment, and
his/her history is return to the card room.
2.3 Document used in the existing system
The existing clinical information management system in Nigist Eleni Hospital uses the
following documents and forms

16
Prescription paper

17
Laboratory form

18
Urine analysis test request and report form

19
Pathology order and report form

20
History sheet

21
Parasitological test request and report form

22
 2.4 users of the existing system
An existing system of Nigist Eleni Hospital has different actors to carry out its job.

Among those actors, the most common are:

 Doctors
The doctors write down and see the patient`s history, treats them, and send his/her
to the various diagnostic department for further examination.

 Patient
The patient gives true information to the doctor, recorder, and other rooms to get
successful treatment.
It gives samples like urine, blood, sputum, and stool in the laboratory room.
 Recorder
 The Recorder register the patient information and search the patient information
from the store to send this data like Out Patient Department, Eye unit, Dental Room,
and Dermatology Room.
 Laborarorist

Return the result coming from doctors to additional check

 X-ray specialist
 CT-scan specialist
 ultrasound specialist
 dermatologist
 dentists
 Ophthalmologist
 Nurses
 Midwiferist
 Trajiary

2.5 drawback of the existing system

The existing system of Nigist Eleni Hospital has the following drawback:

 Loss of patient information:

 Wasting of time:
 Tedious
 Switching of patent information
 Send patient information to the wrong room

2.6 Business rules of the domain

The existing system has its method in which system users are treated.

23
BR1.patient information not seen by another person without permission

BR2.The patient should express her/his pain to doctors

BR3.patients must be there in queue order to get service

BR4.patients must be registered and takeout card from Hit Department to get service

2.7 Alternative solution

The members of our project team have come up with the following possible solutions to the
systemic problem at Nigst Eleni Mohammed Hospital.
 Web based Clinical Information Management System
 Android based Clinical Information Management System
 Desktop based Clinical Information Management System
Therefore, our team selected web based clinical information management system
because this applications can be accessed from any computer through the internet,
instead of having to be individually installed on each computer that you wish to
access it from.

24
 CHAPTER THREE
3. PROPOSED SYSTEM
3.1 Introduction
System analysis is an essential activity that must be taken in any project in order to have a clear idea
of a proposed system. In other word, it means the process of analyzing a task to develop a
conceptual model that can be used to complete our task. This implies finding and describing the
object or the problem domain of the system. This chapter will discuss details of the requirement of
the organization, the description and the workflow of each step.
The analysis phase defines the requirement of the system independent of how this requirement will
be accomplished. This phase defines the problem that we will try to solve and explores about the
new system of our project ideally the chapter states in a clear and precise fashion what is to be built.
Analysis focuses on producing a model of the system, called the analysis model,
The analysis model is composed of three individual models:
 Functional model-represented by use cases and scenarios
 Analysis object model-represented by class and object diagrams
 Dynamic model-represented by state machine &sequence Diagram

3.2. Functional requirement

A Functional Requirement (FR) is a description of the service that our coming software must offer. It
describes a software system or its component. A function is nothing but inputs to the software
system, its behaviour, and outputs. Data manipulation, business process, user interaction, or any
other specific functionality which defines what function a system is likely to perform. Functional
Requirements in Software Engineering are also called Functional Specification.
Generally, our system has the following functionalities
 The system should register the patient information
 The system should search patient information
 The system should send patient information to Opd and Pediatric Room
 The system should send urine request
 The system should send parasitology request form
 The system should send blood request form
 The system should view final urine result
 The system should view final parasitology result
 The system should view final blood result
 The system should view patient history
 The system should delete patient information
 The system should update patient information

25
3.3. Non- Functional requirement
Non-Functional Requirements are the constraints or the requirements imposed on the system.
They specify the quality attribute of the software. Non-Functional Requirements deal with issues
like scalability, maintainability, performance, portability, security, reliability, and many more. Non-
Functional Requirements address vital issues of quality for software systems.

3.3.1. User interface

User Interface Design is concerned with the dialogue between a user and the computer. It is
concerned with everything from starting the system or logging into the system to the eventually
presentation of desired inputs and outputs. The overall flow of screens and messages is called a
dialogue.
Our team will implement user-friendly system that fulfills:-
1. The system user should always be aware of what to do next.
2. The screen should be formatted so that various types of information, instructions and
messages always appear in the same general display area.
3. Message, instructions or information should be displayed long enough to allow the
system user to read them.
4. Use display attributes sparingly.
5. Default values for fields and answers to be entered by the user should be specified.
6. A user should not be allowed to proceed without correcting an error.

3.3.2. Hardware consideration

Hardware consideration refers to the physical parts of a computer and related devices.
 Processor: Minimum 1 GHz; Recommended 2GHz or more.
 Ethernet connection (LAN) OR a wireless adapter (Wi-Fi)
 Hard Drive: Minimum 32 GB; Recommended 64 GB or more.
 Memory (RAM): Minimum 1 GB; Recommended 4 GB or above.
Our system needs the above hardware for installation.

3.3.3. Software consideration

 It is important to be mindful of a few key points when considering a change from
one software solution to another.
Our system works properly in any browsers and smart phones since, it requires only to pass
the URL to the browser.

3.3.4. Performance consideration

System performance is the amount of useful work done by a system - measured by the production
speed of products of a predefined quality.

26
  There shall take less time in various ways of retrieving and processing data
 The system shall minimize errors and should display clear error message that guides
users.
 For login in to the system password and user name should be matched to the password
and name.

3.3.5. Reliability
Reliability is concern with the extent to which the software system consistently performs the
specified functions without failure. Our system is reliability because the system robust enough to
have a high degree of fault tolerance. For example, if the user enters an invalid information, the
system should identify the invalid input and produce a suitable error message.

3.3.6. Error handling

 If there is any error in any window or module, then it should not affect the remaining
part of the software.

3.3.7. Security
 The system shall provide high level of security by blocking an authorised user to view
secured system page.
 The external security should be provided by giving login authentication.

3.4. SYSTEM MODEL

3.4.1Scenarios
The clinical information management system registers patient information, send information from
record room to opd , send urine test request to laboratory ,update patient information , view patient
history, send final urine test result, send blood test request , send blood test final result.

3.4.2. Actor Identification

The actor is an external agent that interacts with the system. The following are actors of the
proposed Clinical information Management system: -
Admin: - a person who is responsible for administer system, Create account, Modify account, update
patient information, delete patient information.
Card Room officer:- a person who is responsible for register patient information ,search patient
information ,send patient information to necessary room.
OPD Room doctor :- a person who is responsible for view and write patient history, view blood
result , view parasitology result, send blood request , send urine request, send x-ray request, view x-
ray final result.

27
Paediatric Room doctor a person who is responsible for view and write patient history, view blood
result , view parasitology result, send blood request , send urine request, send x-ray request, view x-
ray final result.

Laboratory Room:- a person who is responsible for receive blood request, prepare and send blood
final result.
X-Ray room:- a person who is responsible for receive x-ray request ,prepare and send x-ray final
result
Ultrasound:- a person who is responsible for receive ultrasound request ,prepare and send
ultrasound final result.

3.4.3 Use-Case Identification

Use-case model consists of the collection of all actors and all use case, a use case is a scenario that
describes the use of the system by an actor to accomplish a specific goals, an actor is a user playing a
role with respect to the system. Scenario is a sequence of step that describes the interaction
between an actor and the system.
 Use cases
o UC-01:-Login
o UC-02:-Register patient information
o UC-03:-send patient information
o UC-04:-search patient
o UC-05:-send blood request form
o UC-06:-send x-ray request form
o UC-07:-send urine request form
o UC-08:-view blood result
o UC-09:- view parasitology result
o UC-10:-view urine result
o UC-11:-fill and send urine result
o UC-12:- fill and send parasitology result
o UC-13:- fill and send blood result
o UC-14:-view blood request form
o UC-15:- view parasitology request form
o UC-16:- view x-ray request form
o UC-17:-fill and send x-ray result
o UC-18:-view ultrasound request form
o UC-19:-Fill and send ultrasound result
o UC-20:- view patient history
o UC-21:- update patient history

28
3.4.3. Use case model
Use case diagram shows the interaction between the actors and the use cases which are
found in our proposed system. Use case diagrams describe what a system does from the
viewpoint of an external observer. A scenario is an example of what happens when someone
interacts with the system. Our system is represented using a use case diagram in the figure
below:

3.5. Dynamic model

3.5.1. Sequence diagram

A UML sequence diagram is used primarily to show the interactions between objects in the
sequential order that those interactions occur. The main purpose of a sequence diagram is to
define event sequences that result in some desired outcome. The focus is on messages
themselves and more on the order in which messages occur; nevertheless, most sequence
diagrams will communicate what messages are sent between a system's objects as well as the
order in which they occur.
Sequence diagram for Login Looks like as Follows:-

29
 Fig Sequence diagram for patient registration

Fig Sequence diagram for laboratory receive blood request

Fig Sequence diagram for OPD send blood request

3.6.2. Activity diagram

Activity diagram is basically a flow chart to represent the flow form one activity to another activity.

30
The activity can be described as an operation of the system. The control flow is drawn from one
operation to another. This flow can be sequential, branched or concurrent. The basic purposes of
activity diagrams are similar to other four diagrams. It captures the dynamic behaviour of the
system.
Activity Diagram for laboratory view info looks like as follows

31
Activity Diagram for l looks like as follows

Activity Diagram for paediatric looks like as follows

Activity Diagram for Ultrasound looks like as follows

32
Activity Diagram for x-ray looks like as follows

33
Reference

34