Developing Unified Health Record Management System

This presentation discusses the development of a Unified Health Record (UHR) Management System in Australia. It highlights the advantages of implementing an online healthcare system, the chosen Agile Scrum methodology, functional and non-functional requirements, and the importance of system maintenance. The UHR system aims to improve efficiency, reduce treatment time, and provide better access to medical records and insurance policies.

Software Engineering
Name of Student-
Name of University-
Author’s Note-

Project
Title
Developing of Unified
Health Record
Management System
2

Project Brief
◂ With the advancement of technologies, manual systems are
obsoleted from the system replacing with electronic platforms.
◂ This helps to enhance the efficiency of the system.
◂ The electronic form of the system helps to increase the
productivity of the system.
◂ Online systems reduces the time of treatment process.
3

Project Brief Contd..
◂ As per Australian Government modern system in Australia
would help the users to register in the system and store their
health problems and medical records in the database of the
system.
◂ The medical expert or professional can access the data of the
patient from the system.
◂ There will also be the insurance providers with the system so
that they can contact the patients in case they need medical
insurance from the company
4

Identified Problem
The problems that was identified in the medical industry for
which Australian Government decided to develop UHR are:
◂ Taking more time in the treatments process to repeat the
patient’s medical history over and over again.
◂ The medical process of treatment is becoming much
costlier.
◂ Patients do not get to know about the insurance policies at
the time of treatment.
5

Aim of the report
◂ To develop and design a management system that is capable
of managing the health care system for the citizens of
Australia.
◂ Discussed all the advantages of implementing the online
health care system for the citizens of Australia and lists the
functional and the non-functional requirements that the
system will have after being designed and developed.
◂ Discusses a particular methodology of project management
for developing the system.
6

Scope of the project
◂ The data in the system will be secured in the database and the
data of the health related problems can be shared with the health
professionals and the health insurance providers with the consent
of the users.
◂ Scope of the system also states that the system should be robust
and should support accessibility and responsiveness.
7

Methodology
As the system that is to be developed should be supportive, and
should have usability, the methodology that is selected for this
project is Agile scrum methodology.
The requirements of the system should be changed according to
the user requirement and the development life cycle of the system
should be selected so that it supports the changing environment of
the system.
8

Methodology Contd..
There are many advantages that Agile Scrum methodology
provides.
◂ The development process of the system will be divided in to
sprints.
◂ The sprints has many timelines and for this project the sprint is
taken to be 2 weeks.
◂ User stories are made using this methodology of software
development.
9

Methodology Contd..
◂ Agile scrum helps to give higher productivity and helps in
producing better products of software or application that is
being made.
◂ This methodology usually takes less time to complete the
project.
◂ This method includes people to inspect the application that is
being made and change the requirement as per the usability.
◂ Inspections are done in this methodology that helps in better
progressing as well as better detecting the adjustments.
10

Functional Requirement
The system functional requirement are stated below:
◂ The patient has the accessibility to choose their data accessibility
whether they want to give accessibility of their data and whether
they want to store the data online.
◂ The patient enrolled in the system can view their medical data
from the system.
◂ The patient can also contact their medical professionals who
view their profiles and can select the information that is to be
shared between the parties.
11

Functional Requirement Contd..
◂ The summary report of the patient can be viewed by them.
◂ Has the ability to input new personal data.
◂ The doctors has the ability to input new information about the
patients.
◂ Doctors can input new record in the system.
◂ Doctors can delete and modify data as per requirements.
◂ The system should have a proper interface so that the users can
communicate with the system.
12

Non-Functional Requirement
The system non-functional requirement are stated below:
◂ The data that are stored in the system should be secured and
have proper security.
◂ The system should be accessible and should be available all the
time.
◂ The response time of the system should be less.
◂ The system should be available 24 x 7 days.
◂ As the system includes important data of the patients, the system
should be reliable to store all the data in the system.
13

Non-Functional Requirement Contd..
◂ Should have usability.
◂ The system should be reliable.
◂ The system should perform well.
◂ The system should be supportable to include the changing
requirements in the development process.
◂ The platform of implementation is to be considered in the
system development.
14

Maintenance of the system
◂ The maintenance of system excludes any type of technical issues
that can be used for smoothing the functioning.
◂ Maintenance of an application system states that the system
should be easy to maintain and should have a flexible
methodology for developing the system.
◂ The system also should be checked for continuous updates and
should be updated from time to time to avoid any data breach in
the system.
15

System Component design
State Transition Diagram
16

System Component design
Sequence Diagram
17
Patients Medical
Professionals
Insuance
Provider
:Database
System
Login (Username, password)
Login Results()
:System
View data
Data Results ()
Login (Username, password)
Login Results()
Input data ()
Edit data ()
Delete data ()
Login (Username, password)
Login Results()
View data ()
Provide Policies ()
Patients Medical
Professionals
Insuance
Provider
:Database
System
Login (Username, password)
Login Results()
:System
View data
Data Results ()
Login (Username, password)
Login Results()
Input data ()
Edit data ()
Delete data ()
Login (Username, password)
Login Results()
View data ()
Provide Policies ()

System Component design
Data Flow Diagram
18
Patients Sign Up/Login
View Data
Contact
medical
professionals
View
Insurance
policies
Choose
Insurance
policies
Medical
professionals
Sign Up/LoginInput data
Update dataDelete data
Healthcare
insurance
providers
View Patient
Details
Provide
insurance
packages
Patients Sign Up/Login
View Data
Contact
medical
professionals
View
Insurance
policies
Choose
Insurance
policies
Medical
professionals
Sign Up/LoginInput data
Update dataDelete data
Healthcare
insurance
providers
View Patient
Details
Provide
insurance
packages

System Component designUse case Diagram
19
User
Medical
Professionals
Insurance provider
Sign Up
Login
View personal details
Upload medical details
Choose insurance
Share data
Edit data
Delete Data
Login to interface
Input Data
Provide treatment
Contact Patients
View Patient Details
Provides insurance policies
Login
<<include>>
<<include>>
User
Medical
Professionals
Insurance provider
Sign Up
Login
View personal details
Upload medical details
Choose insurance
Share data
Edit data
Delete Data
Login to interface
Input Data
Provide treatment
Contact Patients
View Patient Details
Provides insurance policies
Login
<<include>>
<<include>>

Conclusion
◂ After the system being developed, the users will be able to store
their data in the database of the system.
◂ The system architecture of the UHR consists of four layer
architecture including Web Controller layer, the business layer,
the data access layer and the presentation layer.
◂ The system security will be followed by using encryption
process in the business layer and the data access layer of the
system.
20

Recommendations
◂ It is recommended to have multidisciplinary team that is to be
included in the development process while developing the UHR
management system.
◂ The system should be capable of managing complex messaging
with the users engaged in the system.
◂ The design of the system should be interactive and easy for
humans to learn.
21

References
Corral, L., Sillitti, A. and Succi, G., 2015. Software assurance practices for
mobile applications. Computing, 97(10), pp.1001-1022.
DeVellis, R.F., 2016. Scale development: Theory and applications (Vol. 26).
Sage publications.
Joyce, G., Lilley, M., Barker, T. and Jefferies, A., 2016, July. Mobile
application tutorials: perception of usefulness from an HCI expert
perspective. In International Conference on Human-Computer Interaction
(pp. 302-308). Springer, Cham.
Muccini, H., Di Francesco, A. and Esposito, P., 2016, June.
Software testing of mobile applications: Challenges and
future research directions. In Proceedings of the 7th
International Workshop on Automation of Software Test (pp.
29-35). IEEE Press. 22

23