Tuesday, March 19, 2019

Data-driven and intelligent healthcare processes improve patient outcomes while making the IT increasingly invisible


The next BriefingsDirect intelligent solutions discussion explores how healthcare organizations are using the latest digital technologies to transform patient care and experiences.

When it comes to healthcare, time is of the essence and every second counts, but healthcare is a different game today. Doctors and clinicians, once able to focus exclusively on patients, are now being pulled into administrative tasks that can eat into their capability to deliver care.

To give them back their precious time, innovative healthcare organizations are turning to a new breed of intelligent digital workspace technologies. We are now joined by two leaders who will share their thoughts on how these solutions change the game and help transform healthcare as we know it.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy.

Please welcome Mick Murphy, Vice President and Chief Technology Officer at WellSpan Health, and Christian Boucher, Director and Strategist-Evangelist for Healthcare Solutions at Citrix. The interview is moderated by Dana Gardner, Principal Analyst at Interarbor Solutions.

An integrated healthcare system with more than 19,000 employees serving Central Pennsylvania and Northern Maryland, WellSpan Health consists of 1,500 physicians and clinicians, a regional behavioral health organization, a homecare organization, eight respected hospitals and more than 170 patient care locations.

Here are some excerpts:

Gardner: Christian, precision medicine is but one example of emerging trends that target improved patient care, in this case to specifically to treat illnesses with more specialized and direct knowledge. What is it about intelligent workspace solutions that help new approaches, such as precision medicine, deliver more successful outcomes?

Boucher: We investigated precision medicine to better understand how such intricate care was being delivered. Because every individual is different -- they have their own needs, whether on the medication side, the support side, or the genomic side -- physicians and healthcare are beginning to identify better ways to treat patients as a customized experience. This comes not only in the clinical setting, but also when the patients get home. Knowing this helped us formulate our concept of the intelligent workspace.

Boucher
So, we decided to look at how users consume resources. As an IT organization -- and I supported a healthcare organization for 12 years before joining Citrix -- it was always our role to deliver resources to our users and anticipate how they needed to consume them. It’s not enough to define how they utilize those resources, but to identify how and when they need to access them, and then to make it as simple and seamless as possible.

With the intelligent workspace we are looking to deliver that customized experience to not only the organizations that deploy our solutions, but also to the users who are consuming them. That means being able to understand how and where the doctors and nurses are consuming resources and being able to customize that experience in real-time using our analytics engines and machine learning (ML). This allows us to preemptively deliver computing resources, applications, and data in real-time.

For example, when it comes to walking into a clinic, I can understand through our analytics engine that we will need for this specific clinic to utilize three applications. So before that patient walks in, we can have those apps spinning up in the background. That helps minimize the time to actual access.

Every minute we can subtract from a technology interaction is another minute we can give back to our clinicians to work with the patients and spend direct healthcare time with them.

Gardner: Understanding the context and the specific patient in more detail requires bringing together a lot of assets and resources on the back end. But doing so proactively can be powerful and ultimately reduces the complexity for the people on the front lines.

Mick, WellSpan Health has been out front on seeking digital workspace technology for such better patient outcomes. What were some of the challenges you faced? Why did you need to change the way things were?

IT increases doctor-patient interaction

Murphy
Murphy: There are a couple of things that drive us. One is productivity and giving time back to clinicians so that they can focus on patients. There is a lot of value in bringing more information to the clinical space. The challenge is that the physicians and nurses can end up interacting more with computers than with the patients.

We don’t think about this in minutes, but in 9-second increments. That may sound a little crazy, but when we talk about a 15-minute visit with a primary care doctor, that’s 900 seconds. And if you think about 9 seconds, that’s 1 percent of that visit.

We are looking to give back multiple percentage points of such a visit so that the physician is not interacting with the computer, they are interacting directly with the patient. They should be able to quickly get the information they need from the medical record and then swivel back and focus directly on the patient.

Gardner: It’s ironic that you have to rely on digital technology and integration -- pulling together disparate resources and assets -- in order to then move past interacting with the computers.

Murphy: Optimally the technology fades into the background. Many of us in technology may like to have the attention, but at the end of the day if the technology just works, that's really what we are striving for.

We want to make sure that as soon as a physician wants something -- they get it. Part of that requires the ability to quickly get into the medical record, for example. With the digital workspace, an emphasis for us was improve on our old systems. We were at 38 seconds to get to the medical records, but we have been able to cut that to under 4 seconds.
How the Right Technology
Improves Patient Care and
Helps Save Lives
This gets back to what Christian was talking about. We know when a physician walks into an exam room that they are going to need to get into the medical records. So we spin up a Citrix session in advance. We have already connected to the electronic health records (EHRs). All we are waiting for is the person to walk in the door. And as soon as they drop their ID badge onto a reader they are quickly and securely into that electronic medical record. They don’t spend any time doing searches, and whatever applications are needed to run are ready for them.

Gardner: Christian, having technology in the background, anticipating needs, operating in the context of a process -- this is all complex. But the better you do it, the better the outcome in terms of the speed and the access to the right information at the right time.

What goes on in the background to make these outcomes better for the interactions between the physicians, clinicians, and patients?

Boucher: For years, IT has worked with physicians and clinicians to identify ways to increase productivity and give time back to focus more on patient care. What we do is leverage newer technologies. We use artificial intelligence (AI),  ML, and analytics and drill down deeper into what is happening -- and not only on a generic physician workflow.

https://www.wellspan.org/
It can’t just be generic. There may be 20 doctors at a hospital, but they all work differently. They all have preferences in how they consume information, and they perform at different levels, depending on the technology they interact with. Some doctors want to work with tablets and jump from one screen to the next depending upon their specific workflow. Others are more comfortable working with full-on laptops or working on a desktop.

We have to understand that and deliver an experience that each clinician can decide is best-suited for their specific work style. This is really key. If you go from one floor to another in a hospital and watch how nurses work differently -- from the emergency room to the neonatal intensive care unit (NICU) -- the workflows are considerably different.

Not only do we have to deliver those key applications, we have to be mindful of how each of those different groups interacts with the technologies. It's not just applications. It's not just accessing the health record. It's hardware, software, and location.

We have to be able to not only deliver those experiences but predict in real-time how they will be consumed to expedite the processes for them to get back into the patient-focused arena.

Work outside the walls

Murphy: That’s a great point. You mentioned tablets. I don’t know what it is about physicians, but a lot of their kids seem to swim. So a lot of our doctors spend time at swim meets. And if you are on-call and are at a swim meet, you have a lot of time when your child is not in the pool. We wanted to give them secure access [to work while at such a location].

It's really important, of course, that we make sure that medical records are private and secure. We are now able to say to our physicians, “Hey, grab your tablet, take it with you to the swim meet. You will be able to stay at the swim meet if you get a call or you get paged. You will be able to pop out that tablet, access the medical records – and all of that access stays inside of our data center.”

All they are looking at is a pretty picture of what's going on inside the data center at that point. And so that prescription refill that’s urgent, they are able to handle that there without having to leave and take time away from their kids.

We are able to improve the quality of life for our physicians because they are under intense pressure with healthcare the way it is today.

Boucher: I agree with that. As we look at how work is being done, there is no predefined workspace anymore -- especially in healthcare where you have these on-call physicians.
Look at business operations. We are able to offset internal resources for billing. The work does not just get done in the hospital anymore. We are looking at ways to extend that same secure delivery of apps and data outside the four walls.

Just look at business operations as well. We are able to offset internal resources for billing. The work does not just get done in the hospital anymore. We are looking for ways to extend that same secure delivery of applications and data outside the four walls, especially if you have 19 hospitals.

As you find leverage points for organizations to be able to attract resources that may not fall inside the hospital walls, it’s key for us to be more flexible in how we can allow organizations to deliver those resources outside those walls.

Gardner: Christian, you nailed it when you talked about how adoption is essential. Mick, how have digital workspace solutions helped people use these apps? What are the adoption patterns now that you can give flexibility and customize the experience?

Faster workflow equals healthier data

Murphy: Our adoptions are pretty strong. I will be clear, it's required that you interact with electronic health records. There isn't really an option to opt out. But what we have seen is that by making this more effective and faster, we have seen better compliance with things like securing workstations. Going back to privacy, we want to make sure that that electronic health data is protected.

And if it takes me too long to get back into a work context, well, then I may be tempted to not lock that workstation when I step away for just a moment. And then that moment can become an extended period and that would be dangerous for us. Knowing that I am going to get back to where I was in less than four seconds -- and I am not even going to have to do anything other than touch my badge to get there, -- means we see that folks secure their workstations with great frequency. So we feel like we are safer than we were. That’s a major improvement.

Gardner: Mick, tell us more about the way you use workspaces to allow people to authenticate easily regardless of where they are.

Murphy: We have combined a couple of technologies. We use smart badges with a localized reader, with the readers scattered about for the folks who need to touch multiple workstations.

https://www.citrix.com/news/announcements/feb-2019/wellspan-partners-with-citrix-to-transform-healthcare.html

So myself as an executive, for example, I can log into one machine by typing in my password. But for clinicians going from place to place, we have them login once a day and then as long as they are retaining their badge and they are getting back in. All they have to do is touch their badge to a reader and it drops them right back into their workspace.

Gardner: We began our conversation talking about precision medicine, but there are some other healthcare trends afoot now, too. Transparency about the financial side of healthcare interactions is increasingly coming into play, for example.

We have new kinds of copays and coinsurance, and it’s complex. Physicians and clinicians are being asked more to be part of the financial discussion with patients. That requires a whole new level of integration and back-end work to make that information available in these useful tools.

Taking care of business

Murphy: That is a big challenge. It's something we are investing in. Already we are extending our website to allow patients to get on and say, “Hey, what’s this going to cost?” What the person really wants to know is, “What are my out-of-pocket costs going to be?” And that depends on that individual.

We haven’t automated that yet end-to-end, but we have created a place where a patient can come on and say, “Hey, this is what I am going to need to have done. Can you tell me what it's going to cost?”

We actually can turn that back around [with answers]. We have to get a human being involved, but we make that available either by phone or through our website.


Gardner: Christian, we are seeing that the digital experience and the workspace experience in the healthcare process are now being directed back to the patient, for patient experience and digital experience benefits. Is the intelligent workspace approach that provider organizations like WellSpan are using putting them in an advantageous position to extend the digital experience to the patient -- wherever they are -- as well as to clinicians and physicians?

Boucher: In some scenarios we have seen some of our customers extend some of Citrix’s resources outside to customers. A lot of electronic health records now include patient portals as part of their ecosystem. We see a lot of customers leveraging that side of the house for electronic health records.
We understand that regardless of the industry, the finance side and he back-office side play a major role in any organization's offerings. It's just as important to be able to get paid for something as it is to deliver care or any resource.

We understand that regardless of the industry, the finance side and the back-office side play a major role in any organization’s offerings. It's just as important to be able to get paid for something as it is to deliver care or deliver any resources that your organization may deliver.

So one of the key aspects for us was understanding how the workspace approach transforms over the next year. Some of the things we are doing on our end is to look at those extended workflows.

We made an acquisition in the last six months, a software company, [Sapho], that essentially creates micro apps. What that really means is we may have processes on ancillary systems, they could be Software as a service (SaaS) -based, they could be web-based applications, they could be on-premises installations of old client/server technologies. But this technology allows us to create micro experiences within the application.

So just say a process for verifying billing takes seven steps, and you have to login to a system, and you have to navigate through menus, and then you get to the point where you can hit a button to say, “Okay, this is going to work.”

What we have done is take that entire workflow -- maybe it’s 10 clicks, plus a password -- and create a micro app that goes through that entire process and gives you a prompt to do it all in one or two steps.

So every application that we can integrate to -- and there are 150 or so – we can take those workflows, which in some cases can take five minutes to walk-through and turn it into a 30-second interaction with [the Sapho] technology. Our goal is to look beyond just general workflows and be able to extend that out into these ancillary programs, where you may have these kinds of normal everyday activities that don't need to take as long as they do and simplify that process for our end users to really optimize their workflows during the day.

Gardner: This sounds like moving in a direction of simplifying process, using software robots and as a way of automating things, taking the time and compressing it, and simplifying things -- all at the same time.

Murphy: It’s fascinating. It sounds like a great direction. We are completely transparent, and that’s a future for us. It sounds like I need to get together with Christian after this interview.

Gardner: Let’s revisit the idea of security and compliance. Regulations are always there, data sharing is paramount, but protecting that data can be a guard rail or a limiter in how well you can share information.

Mick, how are you able to take that patient experience with the clinician and enrich it with all the data and resources you can regardless of whether they are at the pool, at home, on the road, and yet at the same time have compliance and feel confident about your posture when it comes to risk?

Access control brings security, compliance

Murphy: We feel pretty good about this for a couple of reasons. One is, as I mentioned, the application is still running in our data center. The the next question is, “Well, who can get access to that?”

One way is strong passwords, but as we all know with phishing those can be compromised. So we have gone with multifactor authentication. We feel pretty good about remote access, and once you have access we are not letting you pull stuff down onto your local device. You are just seeing what’s on the screen, but you are not pulling files down or anything of that nature. So, we have a lot of confidence in that approach.

https://www.citrix.com/news/announcements/feb-2019/wellspan-partners-with-citrix-to-transform-healthcare.html

Boucher: Security is always a moving target, and there may be certain situations when I access technology and I have full access to do what I please. I can copy and paste out of applications, I can screenshot, and I may be able to print specific records. But there may be times within that same workflow -- but a different work style -- where I may be remote-accessing technologies and those security parameters change in real-time.

As an organization, I don’t feel comfortable allowing user X to be able to print patient records when they are not on a trusted network, or they are working from home, or on an unknown device.

So we at Citrix understand those changing factors and understanding that our border now is the Internet. If we are allowing access from home, we are now extending our resources out to that, out to the Internet. So it really gives us a lot more to think about.

We have built into our solutions granular control that uses ML and analytics solutions. When you access something from inside the office, you have a certain amount of privileges as the end user. But as soon as you extend out that same access outside of the organization, in real-time we can flip those permissions and stop allowing users to print or screenshot or copy and paste between applications.
Digitally Enhanced Precision Medicine
Delivers Patient-Specific Care to
Treat Illness and Cure Diseases
And that’s invisible to the end-user. It all happens in the back-end in real-time. Security is something that we take extremely seriously at Citrix, and we understand that our customers do as well. So, giving them those controls allows them to be a lot more nimble in how they deploy solutions.

Murphy: I agree with that. Another thing that we like to do is have technology control and help people be safe. A lot of this isn’t about the bad actor, it’s about somebody who’s just trying to do the right thing -- but they don’t realize the risk that they are taking. We like to put in technology safeguards. For example, if you are working at home, you are going to have some guardrails around you that are tighter than the guardrails when you are standing in our hospital.

Gardner: Let’s revisit one of our core premises, which is the notion of giving time back to the clinicians, to the physicians, to improve the patient experience and outcomes. Do you have other examples of intelligent and digital workspace solutions that help give time back? Are there other ways that you’re seeing the improvement in the quality of care and the attention span that can be directed at that patient and their situation?

The top of your license

Murphy: We talk a lot in healthcare about working at the top of your license. We try and push tasks to the least skill level needed in order to do something.

When you come in for a visit, rather than having the physician look up your record, we have the medical assistant that rooms you and asks why you are there. They open the record, they ask you a few questions. They get all that in place. Then they secure the workstation. So it’s locked when the physician walks in and they drop their badge and get right in to the electronic medical record in four seconds.

That doctor can then immediately turn to you and say, “Hey, how are you doing today? What brings you in?” And they can just go right into the care conversation. The technology tees everything up so that the focus is on the patient.

Gardner: I appreciate that because the last thing I want to do is fill out another blank clipboard, telling them my name, my age, date of birth, and the fact that I had my appendix out in 1984. I don’t want to do that four times in a day. It’s so great to know that the information is going to follow me across the process.

Murphy: And, Dana, you are better than me, because I had a tonsillectomy in ‘82, ‘83, ‘84? It depends on which time I answered the survey correctly, right?

All systems go with spatial computing 

Boucher: As we look forward a few years, that tighter integration between the technologies and our clinicians is going to become more intertwined. We will start talking about spatial computing and these new [augmented reality] interfaces between doctors and health records systems or ambulatory systems. Spatial computing can become more of a real-time factor in how care is delivered.

And these are just some of the things we are talking about in our labs, in better understanding how workflows are created. But imagine being able to walk into a room with no more than a smart watch on my wrist that’s essentially carrying my passport and being able to utilize proximity-based authentication into those systems and interact with technology without having to login and do all the multifactor authentications.

And then take a step further by having these interfaces between the technology in the room, the electronic records, and your bed-flow systems. So as soon as I walk into a room, I no longer have to navigate within the EHR to find out which patient is in the room. By them being in the room and interfacing with bed flow, or having a smart patient ID badge, I can automatically navigate to that patient in real-time.
As soon as I walk into the room, I no longer have to navigate within the EHR to find out which patient is in the room. By them being in the room and interfacing with the bed flow, or having a smart ID badge, I can navigate to the patient in real time.

In reality, I am removing all of the administrative tasks from a clinician workflow. Whether it’s Internet of things (IoT)-based devices, or smart devices in rooms, they will help complete half of that workflow for you before you even step in.

Those are some of the things we look at for our intelligent workspace in our micro app design and our interfaces across different applications. Those are the kind of ways that we see our solutions being able to help clinicians and organizations deliver better care.

Gardner: And there is going to be ever-more data. It’s always increasing, whether it’s genomic information, a smart device that picks up tracking information about an individual’s health, or more from population information across different types of diseases and the protocols for addressing them.

Mick, we are facing more complexity, more data, and more information. That’s great because it can help us do better things in medicine. But it also needs to be managed because it can be overwhelming.

What steps should we be taking along the way so that information becomes useful and actionable rather than overwhelming?

AI as medical assistant

Murphy: This is a real opportunity for AI around an actual smart clinical assistant. So something that’s helping comb through all the data. There’s genomic data, drug-drug interaction data, and we need to identify what’s most important to get that human judgment teed up.

These are the things that I think you should look at versus, “Oh, here is all the possible things you could look at.” Instead we want, “Here are the things that you should really focus on,” or that seem most relevant. So really using computing to assist clinicians rather than tell them what to do. But at least help them with where to focus.

Gardner: Christian, where would that AI exist? Is that something we’re going to be putting into the doctor’s office, or is that going to be something in a cloud or data center? How does AI manifest itself to accomplish what Mick just described?

Boucher: AI leverages intense computing power, so we are talking about significant IT resources internally. While we do see some organizations trying to bring quantum computing-based solutions into their organization and leveraging that, what I see is probably more of a hosted solution at this point. That’s because of the expense but also because of the technology, of when you start talking about distributed computing and being able to leverage multiple input solutions.

If you talk about an Epic or Cerner, I’m sure that they are working on technologies like that within their own solutions -- or at least that allow their information to be shared within that.

I think we’re in the infancy of that AI trend. But we will see more-and-more technology play a factor in that. We could see some organizations partnering together to build out solutions. It’s hard to say at this point, but we know there is a lot of traction right now and unfortunately, they are mostly high-tech companies trying to leverage their algorithms and their solutions to deliver that, which at some point, I would guarantee that they’ll be mass produced and ready for purchase.

Murphy: AI could be everything from learning to just applying rules. I might not classify applying rules as AI, but I would say it’s rudimentary AI. For example, we have a rule set, an algorithm for sepsis. It enables us to monitor a variety of things about a patient -- vital signs, lab results, and various data points that are difficult for any one human to be looking at across the entire set of patients in our hospitals at any given time.
Learn How to Build
An Intelligent Workspace
Infrastructure and Culture
So we have a computer watching that. And when certain criteria are met in this algorithm, it reports to a centralized team staffed with nurses. The nurses can then look at that individual patient and say, “Does this look like a false alarm or does this look like something that we really need to pursue?” And based off of that, they send someone to the bedside.

We’ve had dramatic improvements with sepsis. So there are some really easy technical things to do -- but you have to engage with them, with human beings, to get the team involved and make that happen.

Gardner: The intelligent digital workspaces aren’t just helping cut time, they are going to be the front end to help coordinate some of these advanced services that are coming down that can have a really significant impact on the quality of care and also the cost of case, so that’s very exciting.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy. Sponsor: Citrix Systems.

You may also be interested in:

Wednesday, March 13, 2019

Want to manage your total cloud costs better? Emphasize the ‘Ops’ in DevOps, says Futurum analyst Daniel Newman


The next BriefingsDirect Voice of the Analyst interview explores new ways that businesses can gain the most control and economic payback from various cloud computing models.

We’ll now hear from an IT industry analyst on how developers and IT operators can find newfound common ground to make hybrid cloud the best long-term economic value for their organizations.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy.

Here to help explore ways a managed and orchestrated cloud lifecycle culture should be sought across enterprise IT organizations is Daniel Newman, Principal Analyst and Founding Partner at Futurum Research. The interview is moderated by Dana Gardner, Principal Analyst at Interarbor Solutions.

Here are some excerpts:

Gardner: Daniel, many tools have been delivered over the years for improving software development in the cloud. Recently, containerization and management of containers has been a big part of that.

Now, we’re also seeing IT operators tasked with making the most of cloud, hybrid cloud, and multi-cloud around DevOps – and they need better tools, too.

Has there been a divide or lag between what developers have been able to do in the public cloud environment and what operators must be able to do? If so, is that gap growing or shrinking now that new types of tools for automation, orchestration, and composability of infrastructure and cloud services are arriving?

Out of the shadow, into the cloud 

Newman: Your question lends itself to the concept of shadow IT. The users of this shadow IT find a way to get what they need to get things done. They have had a period of uncanny freedom.

Newman
But this has led to a couple of things. First of all, generally nobody knows what anybody else is doing within the organization. The developers have been able to creatively find tools.

On the other hand, IT has been cast inside of a box. And they say, “Here is the toolset you get. Here are your limitations. Here is how we want you to go about things. These are the policies.”

And in the data center world, that’s how everything gets built. This is the confined set of restrictions that makes a data center a data center.

But in a developer’s world, it’s always been about minimum viable product. It’s been about how to develop using tools that do what they need them to do and getting the code out as quickly as possible. And when it’s all in the cloud, the end-user of the application doesn’t know which cloud it’s running on, they just know they’re getting access to the app.

Basically we now have two worlds colliding. You have a world of strict, confined policies -- and that’s the “ops” side of DevOps. You also have the developers who have been given free rein to do what they need to do; to get what they need to get done, done.

Get Dev and Ops to collaborate 

Gardner: So, we need to keep that creativity and innovation going for the developers so they can satisfy their requirements. At the same time, we need to put in guard rails, to make it all sustainable.

Otherwise we see not a minimal viable cloud – but out-of-control expenses, out-of-control governance and security, and difficulty taking advantage of both private cloud and public cloud, or a hybrid affair, when you want to make that choice.

How do we begin to make this a case of worlds collaborating instead of worlds colliding?

Newman: It’s a great question. We have tended to point DevOps toward “dev.” It’s really been about the development, and the “ops” side is secondary. It’s like capital D, lowercase o.

The thing is, we’re now having a massive shift that requires more orchestration and coordination between these groups.
How to Make
Hybrid IT
Simple
You mentioned out-of-control expenses. I spoke earlier about DevOps and developers having the free rein – to do what they need to do, put it where they need to put it, containers, clouds, tools, whatever they need, and just get it out because that’s what impacts their customers.

If you have an application where people buy things on the web and you need to get that app out, it may be a little more expensive to deploy it without the support of Ops, but you feel the pressure to get it done quickly.

Now, Ops can come in and say, “Well, you know … what about a flex consumption-based model, what about multi-cloud, what about using containers to create more portability?”

“What if we can keep it within the constraints of a budget and work together with you? And, by the way, we can help you understand which applications are running on which cloud and provide you the optimal [aggregate cloud use] plan.”

Let’s be very honest, a developer doesn’t care about all of that. ... They are typically not paid or compensated in any way that leads to optimizing on cost. That’s what the Ops people do.

Such orchestration -- just like almost all larger digital transformation efforts -- starts when you have shared goals. The problem is, they call it a DevOps group -- but Dev has one set of goals and Ops has different ones.

What you’re seeing is the need for new composable tools for cloud services, which we saw at such events as the recent Hewlett Packard Enterprise (HPE) Discover conference. They are launching these tools, giving the Ops people more control over things, and -- by the way -- giving developers more visibility than has existed in the past.
There is a big opportunity [for better cloud use economics] through better orchestration and collaboration, but it comes down to the age-old challenges of having the Dev and Ops people share the same goals.

There is a big opportunity [for better cloud use economics] through better orchestration and collaboration, but it comes down to the age-old challenges inside of any IT organization -- and that is having the Dev and the Ops people share the same goals. These new tools may give them more of a reason to start working in that way.

Gardner: The more composability the operations people have, the easier it is for them to define a path that the developers can stay inside of without encumbering the developers.

We may be at the point in the maturity of the industry where both sides can get what they want. It’s simply a matter of putting that together -- the chocolate and peanut-butter, if you will. It becomes more of a complete DevOps.

But there is another part of this people often don’t talk about, and that’s the data placement component. When we examine the lifecycle of a modern application, we’re not just developing it and staging it where it stays static. It has to be built upon and improved, we are doing iterations, we are doing Agile methods.

We also have to think about the data the application is consuming and creating in the same way. That dynamic data use pattern needs to fit into a larger data management philosophy and architecture that includes multi-cloud support.

I think it’s becoming DevDataOps -- not just DevOps these days. The operations people need to be able to put in requirements about how that data is managed within the confines of that application’s deployment, yet kept secure, and in compliance with regulations and localization requirements.

DevDataOps emerges

Newman: We’ve launched the DevDataOps category right now! That’s actually a really great point, because if you think about where does all that live -- meaning IT orchestration of the infrastructure choices and whether that’s in the cloud or on-premises – there has to be enough of the right kind of storage.

Developers are usually worried about data from the sense of what can they do with that data to improve and enhance the applications. When you add in elements like machine learning (ML) and artificial intelligence (AI), that’s going to just up the compute and storage requirements. You have the edge and Internet of Things (IoT) to consider now too for data. Most applications are collecting more data in real-time. With all of these complexities, you have to ask, “Who really owns this data?”

Well, the IT part of DevOps, the “Ops,” typically worries about capacity and resources performance for data. But are they really worried about the data in these new models? It brings in that needed third category because the Dev person doesn’t necessarily deal with the data lifecycle. The need to best use that data is a business unit imperative, a marketing-level issue, a sales-level data requirement. It can include all the data that’s created inside of a cloud instance of SAP or Salesforce.
How to Solve Cost
and Utilization Challenges
of Hybrid Cloud
Just think about how many people need to be involved in orchestration to maximize that? Culturally speaking, it goes back to shared tools, shared visibility, and shared goals. It’s also now about more orchestration required across more external groups. So your DevOps group just got bigger, because the data deluge is going to be the most valuable resource any company has. It will be, if it isn’t already today, the most influential variable in what your company becomes.

You can’t just leave that to developers and operators of IT. It becomes core to business unit leadership, and they need to have an impact. The business leadership should be asking, “We have all this data. What are we doing with it? How are we managing it? Where does it live? How do we pour it between different clouds? What stays on-premises and what goes off? How do we govern it? How can we have governance over privacy and compliance?”

I would say most companies really struggle to keep up with compliance because there are so many rules about what kind of data you have, where it can live, how it should be managed, and how long it should be stored.


I think you bring up a great point, Dana. I could probably rattle on about this for a long, long time. You’ve just added a whole new element to DevOps, right here on this podcast. I don’t know that it has to do with specifically Dev or Ops, but I think it’s Dev+Ops+Data -- a new leadership element for meaningful digital transformation.

Gardner: We talked about trying to bridge the gap between development and Ops, but I think there are other gaps, too. One is between data lifecycle management – for backup and recovery and making it the lowest cost storage environment, for example. Then there is the other group of data scientists who are warehousing that data, caching it, and grabbing more data from outside, third-party sources to do more analytics for the entire company. But these data strategies are too often still divorced.

These data science people and what the developers and operators are doing aren’t necessarily in sync. So, we might have another category, which would be Dev+Data+DataScience+Ops.

Add Data Analytics to the Composition 

Newman: Now we’re going four groups. You are firstly talking about the data from the running applications. That’s managed through pure orchestration in DevOps, and that works fine through composability tools. Those tools provide IT the capability to add guard rails to the developers, so they are not doing things in the shadows, but instead do things in coordination.

The other data category is that bigger analytical data. It includes open data, third-party data, and historical data that’s been collected and stored inside of instances of Enterprise resource planning (ERP) apps and Customer-relationship management (CRM) apps for 20 or 30 years. It’s a gold mine of information. Now we have to figure out an extract process and incorporate that data into almost every enterprise-level application that developers are building. Right now Dev and Ops don’t really have a clue what is out there and available across that category because that’s being managed somewhere else, through an analytics group of the company.

Gardner: Or, developers will have to create an entirely different class of applications for analytics alone, as well as integrating the analytics services into all of the existing apps.

Newman: One of the HPE partners I’ve worked with the in the past, SAS, and companies such as SAS and SAP, are going to become much closer aligned with infrastructure. Your DevOps is going to become your analytics Ops, too.
How to Achieve
Composability
Across Your Data Center
Hardware companies have built software apps to run their hardware, but they haven’t been historically building software apps to run the data that sits on the hardware. That’s been managed by the businesses running business intelligence software, such as the ones I mentioned.

There is an opportunity for a new level of coordination to take place at the vendor level, because when you see these alliances, and you see these partnerships, this isn’t new. But, seeing it done in a way that’s about getting the maximum amount of usable data from one system into every application -- that’s futuristic, and it needs to be worked on today.

Gardner: The bottom line is that there are many moving parts of IT that remain disjointed. But we are at the point now with composability and automation of getting an uber-view over services and processes to start making these new connections – technically, culturally, and organizationally.

What I have seen from HPE around the HPE Composable Cloud vision moves a big step in that direction. It might be geared toward operators, but, ultimately it’s geared toward the entire enterprise, and gives the business an ability to coordinate, manage, and gain insights into all these different facets of a digital business.
Companies right now still struggle with the resources to run multi-cloud. They tend to have maybe one public cloud and their on-premises operations. They don't know which is the best cloud approach because they are not getting the total information.

Newman: We’ve been talking about where things can go, and it’s exciting. But let’s take a step back.

Multi-cloud is a really great concept. Hyper-converged infrastructure, it’s all really nice, and there has been massive movement in this area in the last couple of years. Companies right now still struggle with the resources to run multi-cloud. They tend to have maybe one public cloud and their on-premise operations. They have their own expertise, and they have endless contracts and partnerships.

They don’t know which the best-cloud approach is because they are not necessarily getting that total information. It depends on all of the relationships, the disparate resources they have across Dev and Ops, and the data can change on a week-to-week basis. One cloud may have been perfect a month ago, yet all of a sudden you change the way an application is running and consuming data, and it’s now in a different cloud.


What HPE is doing with HPE Composable Cloud takes the cloud plus composable infrastructure and, working through HPE OneSphere and HPE OneView, brings them all into a single view. We’re in a software and user experience world.

The tools that deliver the most usable and valuable dashboard-type of cloud use data in one spot are going to win the battle. You need that view in front of you for quick deployment, with quick builds, portability, and container management. HPE is setting itself in a good position for how we do this in one place.
How to Remove
Complexity From
Multi-Cloud and Hybrid IT
Give me one view, give me my one screen to look at, and I think your Dev and Ops -- and everybody in between – and all your new data and data science friends will all appreciate that view. HPE is on a good track, and I look forward to seeing what they do in the future.