Creating a Unified Health Record System

This report discusses the creation of a new medical health record system proposed by the Australian government. It covers the requirements, design, and implementation of the system, including data security measures. The system aims to provide healthcare professionals and patients with easy access to health records and improve insurance packages.

Running head: SOFTWARE ENGINEERING FUNDAMENTALS
SOFTWARE ENGINEERING FUNDAMENTALS
Name of the Student
Name of the University
Author Note:

1SOFTWARE ENGINEERING FUNDAMENTALS
Executive Summary
The purpose of the report is all building a new medical health record system for all the citizen of
Australia. By the help of the system, any registered and healthcare professional can have an easy
access to the health records. A part of record will be made available to the healthcare provider. It
is generally done so that they can provide much better insurance package that are helpful to the
people. Australian Government has come up with the idea of design and development of unified
health record management system. The proposed system can be easily used by both patient and
healthcare professionals.

2SOFTWARE ENGINEERING FUNDAMENTALS
Table of Contents
Introduction..........................................................................................................................3
Detail Requirements............................................................................................................3
Requirement Analysis..........................................................................................................4
Analytical Hierarchical Process...........................................................................................5
Use case design................................................................................................................5
Data Flow diagram..........................................................................................................5
E-R diagram.....................................................................................................................5
Data Base Design.............................................................................................................5
Waterfall Model...............................................................................................................5
UI design for making data safe and secure......................................................................7
Requirement solution...........................................................................................................7
Conclusion...........................................................................................................................7
General and Specific Recommendation...............................................................................8
References............................................................................................................................9

3SOFTWARE ENGINEERING FUNDAMENTALS
Introduction
The following report is all about creating new medical health records system which has
been proposed by Australian government. This particular system helps in registration and
approval of healthcare professionals in whole Australia (Muthee et al. 2018). It will be needed
for getting access to the health records at the time of visiting for consultation. A part of the
available record will be made available to the insurance providers so that they can provide better
insurance packages. This particular step will be considered to be helpful to large number of
people (Liu 2016). Australian government has come up with the idea of design and development
of unified health record (UHR) management system.
In the coming pages of the report, an idea has been provided concerning detail
requirements. After that, an analysis has been done for the detail requirements followed by
requirement analysis. An idea has been provided with respect to the waterfall model. UI (User
Interface) design has been discussed which is needed for safety and security of data. The last
section of the report deals with list of recommendation for the new system.
Detail Requirements
Australian Government has come up with some of the requirements which have been put
forward like:
 UHR data needs to completely safe and secure.
 In the design system, the patient needs to have complete control over kind of data which
they want to share with the healthcare professionals (Puttkammer et al. 2016). It is mainly
by healthcare professionals.

4SOFTWARE ENGINEERING FUNDAMENTALS
 The data of healthcare needs to be maintained until the lifetime of user. In this user needs
to keep all the required data up-to-date (Kurniadi and Pratiwi 2017). All the required
healthcare data needs to be deleted soon after the one month after the demise of the
patient.
 Healthcare providers that are insurance providers come up with the ability for getting
access to the summary of the reports (Kasthurirathne et al. 2015). It is mainly provided at
the end of the user visit to the GP.
 Software comes up with mainly three kinds of interfaces where each of the corresponding
entity that is user and healthcare providers help in accessing the record.
Requirement Analysis
Requirement Analysis can be stated as the method of defining the overall expectation of
user (patient) for the given medical record system. It needs to completely build and modified.
Requirement analysis requires all kind of task which help in identifying the need of the
stakeholders (Ali et al. 2016). Requirement analysis can be ultimately defined as analysing,
documentation, validation and managing of various software. At present, there are large number
of requirement analysis techniques like
Business Process Modelling Notation (BPMN): This particular technique is considered
to be very much similar for creation of process flow flowcharts (Laing et al. 2015). Business
process modelling and its notation are mainly needed for creating graphs of business process.
Unified Modelling Language (UML): It mainly comprises of integrated set of given
diagram which can easily visualize and document the artefacts of the software system (Baird and
Boak 2016). This particular technique is needed for object-oriented software along with working
of software development process.

5SOFTWARE ENGINEERING FUNDAMENTALS
Flowchart techniques: A flowchart helps in analysing the sequential flow and control of
list of activities which are completely related to each other. Flowcharts come up with various
kind of formats like top-down and linear (Azaria et al. 2016). Flowchart mainly focuses on
having an easy understanding, which is easily understandable for both technical and non-
technical team members.
Data Flow Diagram (DFD): It is mainly needed for visual representation of given
system and processes which are complex and difficult for describing. DFD aims to provide flow
of information by the help of system or processes (Haskew et al. 2015). It is merely inclusive of
data inputs and outputs and different kind of subprocesses by which the data moves. DFD aims
to describe various kind of entities and relationship by making use of standardization symbols
and notation.
Role activity diagram (RAD): It can be stated role process model which highlights the
role-activity diagram. It can be stated as a high-level view which captures the dynamics and
structure of the organization. Roles are needed for grouping the activities on together platform
into the required units of given responsibilities (Alshamrani and Bahattab 2015). Activities are
known to be basic activity of the role. Any given activity can be carried out on isolation, or even
it may require proper coordination with the given activities with the given role.
Gap Analysis: This particular technique helps analysis of gap in the overall performance
of the medical record system. This is mainly taken into consideration where the business
requirements are completely met or not (Stoica et al. 2016). Gap aims to highlight the differences
which exist between the current state and target state.
Analytical hierarchical process
1) CREATE TABLE Patient (

6SOFTWARE ENGINEERING FUNDAMENTALS
PatientID int,
LastName varchar (255),
FirstName varchar (255),
Address varchar (255),
City varchar (255),
HealthRecord Varchar (500),
JoiningDate Date
);
** The above table query will create a table with table name Patient, including the
attributes shown in the query above.
** The next query will show the details of the patient’s records who have joined the
previous month in the system.
SELECT * FROM Patients WHERE JoiningDate BETWEEN '2019-05-01' AND
'2019-05-31';
The table report that will be generated from the above query is shown below
PatientID LastName FirstName Address City HealthRecor
d
JoiningDate
123 adsf awqr rqrqfsdvdsv afsdf afsvsdvsdv 2019-05-14
345 fbsb wefqwf fqfwefvsdv wefef wfcsvxv 2019-05-15
2) CREATE TABLE Doctor (
DoctorID int,
LastName varchar (255),

7SOFTWARE ENGINEERING FUNDAMENTALS
FirstName varchar (255),
Phone number (10),
City varchar (255),
VisitingDate DATE,
VisitingTime TIME,
Salary number (20)
);
Doctor’s table created by the above query.
To get the details of the doctors, the query that is needed is
SELECT * FROM Doctors;
The above query will display the following shown table
DoctorID LastNam
e
FirstName Phone City VisitingDate VisitingTime Salary
125 jhj ugjb 541313 kjjk 2019-05-14 5:00pm 43137
642 Jnm uthgn 123456 jhmn 2019-05-26 4:00pm 64631
452 rrdg ijkn 1234 kjm 2019-05-27 9:00pm 64613
3) To select the heath description in the system the following query is to be executed.
SELECT * FROM Patients;

8SOFTWARE ENGINEERING FUNDAMENTALS
Design
1) Use Case Design
Figure 1: Use case diagram
(Source: Created by Author)

9SOFTWARE ENGINEERING FUNDAMENTALS
2) Data Flow Diagram
Figure 2: Data Flow diagram
(Source: Created by Author)

10SOFTWARE ENGINEERING FUNDAMENTALS
3) Entity Relationship Diagram
Figure 3: Entity Relationship diagram
(Source: Created by Author)

11SOFTWARE ENGINEERING FUNDAMENTALS
4) Database Design
The database design shown above states the entity relationship diagram of the system of
Unified Health Record. This system has patient table, the doctor table and the insurance
company and the payment table that is shown in the ERD diagram above. The ERD diagram is
normalized in the below diagram.
Figure 4: Entity Relationship diagram in Normalized form
(Source: Created by Author)
Waterfall Model

12SOFTWARE ENGINEERING FUNDAMENTALS
Waterfall model is known to be very first process model which has been introduced till
now. This particular model is also known as linear-sequential life cycle model. This particular
model is very much easy to understand and easy to use (Muthee et al. 2018). In this particular
model, each of the phases is completed just before the very next phase before beginning. There is
no kind of overlapping in the given phases. This particular model focus on software development
process, which is linear sequential flow (Liu 2016). It merely highlights the fact that any given
phase in the development process comes into picture if and only if any phase is completed. In
this particular model, the given phases do not overlap. The phases of waterfall model are
described below like
Analysis and collection of requirement: All the required need of the given new medical
record system which is to be developed are collected in this particular stage.
Design of new medical record system: The requirements specification is done in the very
first phase and followed by this the design of system is proposed (Puttkammer et al. 2016). The
design of new medical system helps in analysing both hardware and system requirements.
Implementation of new medical record system: At the time of input from system design,
the given system is designed developed into small programs which are known to be units
(Kurniadi and Pratiwi 2017). The whole thing is completely integrated into the very next phase.
Integration and Testing of new medical record system: All the required units are
completely developed in the implementation phase of the new medical system (Kasthurirathne et
al. 2015). This particular step is taken at the testing of each of the unit.
Deployment of medical record System: As soon as the functional and non-functional
testing of new medical system is done (Ali et al. 2016). The given system is completely deployed
in the present environment and released in the market.

13SOFTWARE ENGINEERING FUNDAMENTALS
Maintenance of System: There is major number of issues encountered with new medical
record system which comes in the client environment. For tackling such issues, proper kind of
patches are released (Laing et al. 2015). Along with the overall product development for much
better version are released.
UI design for making data safe and secure
User is considered to be as the weakest link in providing security of the system. Most of
the security breaches come into picture as a result of weak password and unencrypted files.
These particular files are left on the system and successful attacks based on social engineering
(Baird and Boak 2016). User is completely tricked for secret information or running codes which
are malicious. Secure human interface design is known to be a complex topic which affects the
operating system as well as the individual programs. Social engineering attacks are considered to
be difficult to fight (Azaria et al. 2016). In this kind of attack, the main notion of attackers is to
fool user who is attacking the attack code or gives up the private information.
Requirement solution
Both the functional and non-functional requirement of this new system has been
described below.
The functional requirement of the new medical record system is
 Both appointment and registration of new patient
 Availability of doctors
 Documentation of health records
 Administration of EMR system
 Patient and Operation Management
 Inventory and Asset Management

14SOFTWARE ENGINEERING FUNDAMENTALS
 Payment and Asset Management.
The non-functional requirement of the system is
 The designed EMR system is available on 24*7 for patient.
 The User interface of the system is very good
 The system will be reliable for its users.
 All stored data will be secured and free from any kind of data breach.
Conclusion
The above pages of help us in reaching to the point that the report focuses creation new
medical record system. Australian government has completely proposed this particular system so
that it can keep track of the medical details. Australian government has come up with the idea of
design and development of unified health record management system. This particular system can
be easily used by patient as well as the healthcare professionals. In the above pages of the report,
a list of requirements has been discussed in details which are needed for maintaining the safety
and security of UHR data. Patient needs to have complete control over the data which they want
to share along with keep of data. In the above pages of the report, the use case diagram and data
flow diagram, database design has been discussed in details. Both waterfall model and user
interface has been discussed have been details which are needed for maintaining safety and
security of data.
General and Specific Recommendation
There is list of recommendation for new medical record system like
 Improving privacy and security practices for the new system.
 Organizational practices for immediate implementation

15SOFTWARE ENGINEERING FUNDAMENTALS
 Security practices for future implementations
 Building an industry wide-security infrastructure.
 Analysis of system issues which are related to privacy and security.

16SOFTWARE ENGINEERING FUNDAMENTALS
References
Ali, S.M., Giordano, R., Lakhani, S. and Walker, D.M., 2016. A review of randomized
controlled trials of medical record powered clinical decision support system to improve quality
of diabetes care. International journal of medical informatics, 87, pp.91-100.
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Azaria, A., Ekblaw, A., Vieira, T. and Lippman, A., 2016, August. Medrec: Using blockchain for
medical data access and permission management. In 2016 2nd International Conference on
Open and Big Data (OBD) (pp. 25-30). IEEE.
Baird, S. and Boak, G., 2016. Leading change: introducing an electronic medical record system
to a paramedic service. Leadership in Health Services, 29(2), pp.136-150.
Haskew, J., Rø, G., Saito, K., Turner, K., Odhiambo, G., Wamae, A., Sharif, S. and Sugishita, T.,
2015. Implementation of a cloud-based electronic medical record for maternal and child health in
rural Kenya. International journal of medical informatics, 84(5), pp.349-354.
Kasthurirathne, S.N., Mamlin, B., Grieve, G. and Biondich, P., 2015. Towards standardized
patient data exchange: integrating a FHIR based API for the open medical record system.
Kurniadi, A. and Pratiwi, R., 2017. Patient Clinical Data Integration in Integrated Electronic
Medical Record System for Health Care Facilities in Indonesia. Jurnal Kesehatan
Masyarakat, 13(2).
Laing, G., Bruce, J., Skinner, D., Allorto, N., Aldous, C., Thomson, S. and Clarke, D., 2015.
Using a hybrid electronic medical record system for the surveillance of adverse surgical events

17SOFTWARE ENGINEERING FUNDAMENTALS
and human error in a developing world surgical service. World journal of surgery, 39(1), pp.70-
79.
Liu, P.T.S., 2016, November. Medical record system using blockchain, big data and
tokenization. In International conference on information and communications security (pp. 254-
261). Springer, Cham.
Muthee, V., Bochner, A.F., Kang’a, S., Owiso, G., Akhwale, W., Wanyee, S. and Puttkammer,
N., 2018. Site readiness assessment preceding the implementation of a HIV care and treatment
electronic medical record system in Kenya. International journal of medical informatics, 109,
pp.23-29.
Puttkammer, N., Baseman, J.G., Devine, E.B., Valles, J.S., Hyppolite, N., Garilus, F., Honoré,
J.G., Matheson, A.I., Zeliadt, S., Yuhas, K. and Sherr, K., 2016. An assessment of data quality in
a multi-site electronic medical record system in Haiti. International journal of medical
informatics, 86, pp.104-116.
Stoica, M., Ghilic-Micu, B., Mircea, M. and Uscatu, C., 2016. Analyzing Agile Development-
from Waterfall Style to Scrumban. Informatica Economica, 20(4).