My Health Record: Cloud-Based Healthcare

This assignment delves into the design and implementation of a cloud-based 'My Health Record' system. It outlines functional and non-functional requirements for securely managing patient health information, including electronic documents, lab reports, and prescriptions. The analysis explores the advantages of this system, such as reduced administrative burdens, cost savings, and improved patient access to their records. It also discusses potential challenges like data security concerns and the need for robust documentation and planning.

qwertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnmqwer
tyuiopasdfghjklzxcvbnmqwertyuiopas
dfghjklzxcvbnmqwertyuiopasdfghjklzx
cvbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyuio
pasdfghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmqwerty
uiopasdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmrty
uiopasdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghjklzxc
Cloud Based Requirements for Headspace

Table of Contents.
Abstract 3
1. Introduction 4
2. Functional and Non-Functional Requirements 4
2.1. Functional Requirements4
2.1.1. Deliberations for “My Health Record” Proposal 4
2.1.2. Structural Design 5
2.1.3. Prerequisites for Cloud-Based Solution 5
2.1.3.1. Implementation of Middleware 5
2.1.3.2. Deployment of Database Server 5
2.1.3.3. Authentication Server 6
2.2. Non Functional Requisites 6
2.2.1. Reliability 6
2.2.2. Usability 6
2.2.3. Performance 6
2.2.4. Cloud Data Security 7
3. Potential and Limitations of Headspace Cloud Implementation 7
4. Advantages and Disadvantages of Predictive SDLC and Adaptive SDLC 9
5. Suggestions 9
6. Conclusion 11
7. Reference 12
2

Abstract
The current era’s buzzword which has been widely carried out in Healthcare enterprise is the
term cloud computing. This report discusses the functional and non-functional requirements of
the patient digital record identified as “My Health Record” that is intended to document the
fitness summary of 12 to 25 mentally sick youths. Besides, the potentials and drawbacks of the
cloud deployment in Headspace are exemplified. And, the suggestions of suitable software
program development life Cycle (SDLC) are also provided for improving the performance of
providing adequate treatment to the patients through Headspace organization.
3

1. Introduction
An electronic health record “My health record” is drafted for retaining the digital synopsis of
mental illness on youths. Healthcare providers and doctors located across various geographical
areas can be able to access this file through cloud. The medication recommendation, patient’s
unreceptive prominence, fitness examination documentation; lab test outcomes, height, body
weight, and other medical conditions provided in this record are accessible by the hospitals
across the globe. The appropriate exploitation of sufferer’s information will let the physicians to
prooffer excellent attributes and detriment concern for the sufferers.
The sufferers staying in countrified regions should have to move prolonged distances for
reaching the healthcare providers by encompassing their paper health records. The
autonomous wellbeing document furthermore does not hold earlier indications in support of
the sufferer documents. Other than that, “My Health Record” affords improved prediction,
earlier wellbeing concern through the physicians all around the world, furthermore effective
medication owing to the exploitation of the cloud technology. However it additionally goes
through the non functional requirements like usability, reliability, security and performance,
which are explained in the sections below.
2. Functional and Non-Functional Requirements
The requisites are whichever functional or non-functional, are demanded in lieu of progressing
any task. Below explained are the functional and non-functional requirements to progress the
Headspace cloud solution.
2.1. Functional Requirements
2.1.1. Deliberations for “My Health Record” Proposal
 Cloud-Based My Health Record: A collection of wellness management knowledge
resources are ensemble towards the larger clouds meant for communicating the
sufferer’s document in simple manner.
4

 Client Authorization: “My Health Record” offered the proprietor permissions headed for
both the sufferers and healthcare provider. They are capable of bestowing validations
established upon their inclinations through keywords.
2.1.2. Structural Design
The organizational cloud architecture for the Headspace health document scheme is
exemplified in the diagram shown below.
2.1.3. Prerequisites for Cloud-Based Solution
The enterprise contains accumulated database server, middleware and validation server for
deploying the external cloud solution in the Headspace organization.
2.1.3.1. Implementation of Middleware
An ordinary platform, which is bargained in favor of the entire wellness documentation scheme,
is nothing but middleware. And, the purpose of the middleware is to substitute the role of
graphical user interface employed to impede the communications amidst the health
management contributors and the accumulated database server. Moreover, middleware is
5

linked up with various health clinics in order to disperse the patient data within the cloud
platform.
2.1.3.2. Deployment of Accumulated Database server
Headspace enterprise incorporates the Infrastructure as a Service (IaaS) cloud service model for
attaining high performance with less security vulnerabilities. Within the IaaS framework,
accumulated database server performs the role of data stockpile to preserve the electronic
wellness documents of multiple patients and to recuperate the sufferer’s information.
2.1.3.3. Validation server Server
The verification course of action is administered through the validation server. The sufferer or
doctor represented as object are authenticated that whether they hold the legible entry for
accessing and modifying the wellness documents of the patients.
2.2. Non Functional Requirements
The non-functional characteristics such as performance, usability, data security, and reliability
for Headspace cloud model are illustrated in the accompanying sections.
2.2.1. Reliability
Notably in health management sectors, reliability is the vital cloud computing component. The
details associated with the patient and wellness evaluation assistance have the admittance to
be retrieved by the contributors devoid of the distractions. The occurrences of disagreements
are familiarized by the clients of digital wellness reports in order to incorporate the cloud
computing solution. Thus within health management provider, the care giver should be able to
login to the legitimate digital wellness document system not including the impact of reliability.
2.2.2. Usability
The inclusion of digital wellness records is extremely provided resistance because of the loss in
usability. The usability characteristics like the client notification and work estimation are
determined in terms of measurements. The measurements associated with the usability are
6

determined by the work assessment. The aforementioned work is done by the health care
contributor group on the cloud vendor system.
2.2.3. Performance
Certain performance concerns related to the wellness report are encountered by the wellness
care contributor. The “My health record” scheme embedded with Headspace should operate
rapidly so as to be acquired by the doctors who are currently in face to face communication
with mental sufferers. Moreover, the performance can be distressed through network
obstructions. Hence, the status of digital record contributor can be impacted because of the
insufficient performance of the cloud scheme. Through the incorporation of external cloud
host, the computer network intrinsic problems can be plagued and thereby the flexibility and
accomplishment of the cloud solution can be improved (Hitachi, 2012).
2.2.4. Cloud Data Security
Data security is the foremost challenge facing the cloud based organizations like Headspace.
Exposure of medical trial data is highly dangerous when compared to other monetary
information. Thus the non functional requirements like data safety and discretion are
eventually necessary.
The data safety standards and procedures described by the wellness management contributor
are essential for assuring the security of sufferer’s information comprised in “My health
record”. Storage space and deliver of protected wellness information generates the vagueness
post the deployment of cloud-based element to the wellness management contributor.
So, the cloud service suppliers make sure that they offer vital safety for the sensitive sufferer’s
details. The safety and confidentiality requirements are not only needed in the distant
information store on the contrary also at the place where the details are disbursed in between
the distant information store and the client (Csiszar, 2014).
3. Positive and Negative implications of Cloud Based Solution
7

The positive and negative features related to the external cloud host solution deployed in
Headspace are delineated in the table below:
Positive Implications Negative Implications
1. The health care provider application can be
retrieved from any location by just utilizing the
devices embedded with the computer
network.
2. Single and immobile computers are not
required to be used by the end users (Saif,
Wani & Khan, 2010).
3. External cloud hosts can also share the
information from cloud model employed in
Headspace.
4. Similar version applications are offered to
all the clients.
5. The older versions of the application
software can be upgraded easily.
6. The application management is turned into
simpler process.
7. The improvement in safety of the data
contained in digital wellness report is
accomplished.
8. The cloud scheme offers the technical
support.
9. Database management process does not
necessarily need any extra ventures.
1. Since the mediating cloud suppliers handles
most of the data sources and other non
functional requirements, the users will not be
aware of the data origin.
2. Attaining faster retorting, openness of
Information and data reimbursement after any
failure is complicated.
3. The service providers possess more
administration capacities when compared to
the end users.
4. The exposure of data exclusive of validation
opens the doors to several security
vulnerabilities.
5. The data recovery and restoration become
complex, due to occurrence of multiple
errands or system failures.
6. The price for acquiring data in case of
failure is higher when contrasted with the
domestic premises.
7. The determination of cost and accessibility
is critical.
8. If any issues are pertained within the
software application or patient information,
the whole centralized database will be
impacted severely.
8

For preventing the negative implications, a valid agreement should be signed among the cloud
users and the cloud service contributors. The medical data and electronic record portal are
highly managed by the cloud suppliers rather than the users (Cristina, 2010). Hence, the
recovering costs and alleviation charges should be the part of the mutual contract.
4. Advantages and Disadvantages of Predictive and Adaptive SDLC
A method for improving the development and quality of the software is defined by the software
development life cycle. The SDLC comprises 6 states of software development namely
requirement plan, requisite analysis, software design, software development, software testing,
and finally software deployment.
Predictive Analysis
The crucial methods such as business proposal, data withdrawal, and creation of resolution are
employed for managing the technology. And, Predictive analysis is one of the best practices to
perform these business activities. The predictive development can be estimated by means of
already existing business trends so as to examine the potential opportunities and threats
(Padhy, Patra & Satapathy, 2012).
Adaptive Analysis
Agile SDLC software model incorporates the adaptive analysis within it. The explanatory
business plan or proposal is not proffered by the adaptive approach rather business
characteristics obsessed growth is the main objective of the approach. Moreover, the
eloquence of the upcoming tasks is not abbreviated.
SDLC Predictive Analysis SDLC Adaptive Analysis
Advantages  Several number of  The changing
9

business procedures
can implement this
approach. So it is
mostly incorporated in
research websites.
 Business
administrators can
procure the idea of
decision making
through this approach.
thereby enhancing the
transactions and
business output
requirements of the
user can be easily
tackled with this
approach.
 High consumption of
time and works are
not involved in this
approach (Ahuja,
Sindhu & Jesus, 2012)
 Assumption of any
requirement is not
required as there is
direct communication
between the
consumers
 The consumers will be
satisfied by the
development of
outstanding software
with extreme quality
in minimum amount of
time
Disadvantages  The business data
centralized decision
forming approach by
the withdrawal of big
data sets is a difficult
process
 The consumer features
 Documenting and
planning processes are
not preferred in this
approach
 Only the technical
expertise can be able
to take this type of
10

are not impacted by
the algorithms at
some point of time
 The customer
requirements changes
over time. This
approach can be able
to cope with the
varying needs
business decision
while developing the
software
5. Suggestions:
The industries related to healthcare and their teams allocated with the technology
management process have higher reliance on the predictive analysis approach for destination
proposal and to build the consumer bonds. For an instance, the cloud organizations like
Amazon and Netflix depend on predictive analytics. Netflix Company analyzes the consumer’s
choice and offers songs, videos, or other media according to that. Hence, depending on the
positive implications of predictive analysis approach, the Headspace organization may
incorporate it for conserving the information security and for enhancing the patient’s
experience.
6. Conclusion:
The functional and non-functional requirements for crafting “My Health Record” schemes are
illustrated in this requirements report. After the adoption of external cloud host, the patient
wellness documents can be managed easily. Moreover, the administration bottlenecks can be
suppressed and the health care costs are reduced further. The acquisition of digital wellness
documents, lab test reports, medicinal prescriptions, etc. can be done authentically. Thus, the
healthcare sectors can be personalized by Headspace organization by virtually and effectively
managing the patient data over the cloud.
11

7. Reference:
Ahuja, P., Sindhu, M. & Jesus, Z. (2012).A Survey of the State of Cloud Computing in Healthcare.
Network and Communication Technologies, 1(2), 12-19.
Cristina, C. (2010). Electronic Health Record Adoption: Perceived Barriers and Facilitators-A
Literature Review. Centre for Military and Veterans’ Health, 1-53.
Csiszar, J. (2014, February 8). Paper-Based Medical Records vs. Electronic Medical Records.
Retrieved from http://www.voices.yahoo.com/paper-based-medical-records-vs-
electronic-medical- 8591569.html
Dinh, H. T., Lee, C., Niyato, D. & Wang, P. (2013).A survey of mobile cloud computing:
architecture, applications, and approaches. Wireless Communications and mobile
computing, 13(8), 1580-1611.
Hitachi (2012). How to Improve Healthcare with Cloud Computing, Hitachi Data Systems, 1-20.
Padhy, R., Patra, M. &Satapathy, S. (2012). Design and Implementation of a Cloud based Rural
Healthcare Information System Model. UNIASCIT, 2 (1), 149-157.
Saif, S., Wani, S., & Khan, S. (2010). A Network Engineering Solution for Data Sharing Across
Healthcare Providers and Protecting Patients’ Health Data Privacy Using EHR System.
Journal of Global Research in Computer Science,2 (8).
12

13