The Internet of Everything is altering not only our personal lives, but also business practices across every major industry – healthcare included. From telehealth to increasing caregiver efficiency to data sharing, the IoE enables opportunities for improvement. But with these new connections and advances in healthcare technology, many physicians and healthcare professionals are skeptical of this new wave of advancements.
How do you appease these apprehensions? Hosting in environments that are HIPAA compliant to start. But consider the opportunities to use large data sets of a population for better treatment.
Cloud opens opportunities to utilize the Internet of Things to better treat cities, states, countries and the entire world. Physicians have begun using multiple devices to track patient information because cloud environments and applications can provide omnipresent access to medical records, as well as increase the opportunity for communication among other physicians. For example, when flu season rolls around, data can be gathered and analyzed from previous seasons to better inform the endangered cities of when the flu season will begin.
Dr. Jeffrey Brenner decided to see where rising healthcare costs were actually being spent; his research is discussed in The Human Face of Big Data.
Brenner, with a memory drive containing the records of 600,000 hospital visits, built a map linking hospital claims to patients’ addresses. He analyzed the patterns of data and the results took him by surprise, about 1,000 people accounted for 30% of hospital bills, because these patients were showing up in the hospital time after time.
Furthering the connection of data and the cloud, when surveyed, 63% of consumers were comfortable with having their medical records stored in the cloud. With movement of the patient record to the cloud, there will be more opportunity to analyze cross population data to better evaluate care protocols and support evidenced based medicine. In addition, when using the cloud to facilitate analyzing patient data, there are more opportunities for collaboration and continuation of care by allowing experts from around the world to share their expertise in a secure and seamless environment. It also allows simplified scalability and the opportunity for expansion for smaller organizations or providers with fewer resources immediately available in non-cloud, on-premises, environments.
As we continue to virtualize more and more aspects of our lives, we will move toward a wholly cloud-based healthcare system. Ahead are the days that healthcare providers will deliver unique patient experiences through cloud-based services securely through purpose-built private and healthcare community clouds.
To read more insights on the cloud, visit our Cloud Perspectives page. Also, be sure to join the conversation – follow @CiscoCloud and use the hashtag #CiscoCloud or leave a comment below.
Read some of our past stories of how cloud and The Human Face of Big Data are changing our personal and professional lives:
Tags: Big Data, CiscoCloud, cloud, connected health, healthcare, HFOBD, himss, HIPAA, Internet of Everything, IoE
The OpenStack Summit for Spring 2014 is scheduled to take place in Atlanta from May 12-16. The general session speaking proposals for the Summit are submitted against the various Summit tracks and the proposed sessions go through a community voting process. While the chairs for each track determine the final list of presentation topics, the voting process is a good way to involve the community to shape the agenda for the Summit. You must be a member of the OpenStack Foundation to vote (join here, if you are not a member). You can start voting here on the various submissions. Voting closes at midnight central time on Monday, March 3.
Many Cisco lead sessions and sessions in collaboration with our partners from other companies have been submitted. The list below captures the details of our submitted talks with hyperlinks to the abstract information. If you find any of the proposals interesting, we urge you to vote for them. Cisco is one of the Premier Sponsors for the OpenStack Summit and we look forward to seeing you in Atlanta.
On January 28th , Cisco launched the Intercloud solutions . On the tail of this announcement, we invited a couple of Cisco Champions to share their perspectives on hybrid cloud and Intercloud with one of our subject matter experts . This was our first Champion podcast.
Eric Wright (@discoposse) and Jonathan Davis (@subnetwork) joined Cisco Mark Loesel to talk about cloud trends, opportunities and challenges companies have to face to deploy a cloud model, and the benefits of intercloud solutions.
Listen to this podcast, hosted by @commsninja.
Amongst the topic covered in this first edition, you will find conversations about
- The evolution of the cloud market
- Embracing hybrid cloud
- When public cloud can’t work for an organization
- The impact of shadow IT
- The importance of security
- The Cisco Intercloud solution and the policy model
- How open do you want your solution to be
- The challenges to the deployment of hybrid cloud
- How cloud will mature
To go further, I encourage you to check the following blogs on Cisco Intercloud- You will find also excellent pointers for additional information.
If you are not familiar with the Cisco Champions, I encourage you to read the blog from Colin Lynch (@UCSGuru) posted last month : What does it mean to be a Cisco Champion?
Tags: cloud, Hybrid Cloud, InterCloud, policy, security
Cloud providers justifiably tout the ease and speed in which services can be implemented, but behind the curtain a dark reality lurks. “Easy on” is a key selling feature of cloud services and for good reason. I well remember leading enterprise application implementation projects in the pre-cloud era. The initial thrill of taking on a major new initiative that could transform the business was quickly overcome by the stark reality of years of highly complex work before going live, only to find out that you were several releases out of date and needed a multi-million dollar upgrade!
In my first major cloud project (to deploy a cloud service management application to 16,000 service engineers) we had users up and running in a couple of months. The business began seeing results quickly and as the software was upgraded we gained advantage of new features immediately. Soon after implementation, we began experiencing problems. It turned out all of the support and operational complexity had been masked from us. Behind the simple outward appearance lay dozens of different software, hardware, data centers and networks. The cloud service provider took first support calls, but getting issues resolved took a long time – and worse, we never were quite sure who was currently working the issue or the status.
Recent studies have identified service and support as the number one decision criteria for customers purchasing new cloud services. In fact, one recent study of the SMB market for cloud services found that the TOP THREE concerns were service related:
- Provide an SLA to ensure application is accessible at all times (53%)
- Provide 24x7 customer support (47%)
- Provide better notification of upgrades, changes and downtime (45%)
Much as cloud providers would like to address these concerns, it’s very difficult operationally to do so because of the multiple back end providers. Cloud customers, in turn, typically use phone, web or email interface with cloud providers to raise and get status on service incidents, so they have no real-time or proactive visibility into issues or outages. As companies put more mission critical applications into the cloud, this dysfunctional support model is causing growing concern and slowing the adoption of cloud services.
Cisco believes the answer is simple. No matter how many different providers might have to get involved to solve a problem, to the original customer it should look like one organization. All information, data and workflows would be shared in an automated way, eliminating manual practices and bottlenecks.
Cisco ServiceGrid enables such integration with a “connect once, connect all” approach, integrating all participants in the support process to the cloud platform only once, instead of integrating everyone one at a time. In speaking with customers who have moved to such a model, they report 40% or more reduction in case resolution times and lower support costs. More importantly, the end user sees what’s happening on the case while it is happening – no finding out hours or days later – resulting in real time SLA’s.
The promise of cloud is incredible, however, cloud customers and cloud service providers need to recognize and address the growing concern about how it will all be supported. Together we can remove a powerful obstacle to cloud adoption, by adding an “easy button” for multi-party support.
source: Techaisle SMB Channel Partner Survey 2012
You may want also to read
Multi-Party Support -- The Emergence of a Dynamic Support Network
Tags: Cisco ServiceGrid, cloud, cloud challenges, cloud services, multi-party support, service delivery, service integration, ServiceGrid
Earlier this month, I attended the first ever summit on OpenDaylight (ODL) project in Santa Clara, CA. This near sold out event was largely successful by many standards. It brought together a large number of great minds to the table to solve some of the toughest challenges the networking industry is facing around Software-defined Networking (SDN) and Network Function Virtualization (NFV). The group announced a first major step forward with the first open source software release called Hydrogen. The bulk of the credit goes to 154 contributors from Cisco, IBM, Ericsson, Red Hat, Citrix and others who wrote over a million lines of code in past ten months to make this happen.
The two-day summit was packed with a variety of sessions that were geared towards a diverse set of audience. The sessions varied from general topics to specific topics such as relevance of Open source software, NFV, LISP, standards, discussions on North and South bound APIs, developer tutorials for building applications & tool chain, using OpenStack with ODL, analytics, test automation, and a true story of SDN in production environment.
Of all these topics, here are the three important themes that stood out to me -
1. The importance of an Open Source, community initiative for SDN
The concept of Open Source software has been around since decades. It is fast catching up in the non-traditional realms of computer networking. For some, the concept of open source equates to free software. While this is partially true, I strongly believe that open=free is a misnomer. I have started to realize that open source and further, the collaborative initiatives like ODL is far beyond the notion of freeness. In my view, the most important thing that such an initiative does is to gather right minds to bring out bright ideas. The collective wisdom that emanates from such a collaborative initiative helps vendors develop a cohesive set of products that speaks a common language, and perhaps share certain fundamental design constructs to aid interoperability. At the same time, I believe that this collaboration helps to compress the infinite ways vendors can built products to a bounded, agreed upon set of behaviors and interfaces. Customers are real beneficiaries of such an open initiative due to this standardization and better product interoperability. As Vijay Pandey from IBM aptly said in one of his presentations, open source initiatives like ODL “promote innovation and raise the value bar.”
Cisco firmly believes in and supports such open source initiatives. Cisco is a platinum member of ODL project, as well as a Gold member of OpenStack Foundation. You can find more information about OpenStack at Cisco , and a rich set of Cisco Services to help you exploit and adopt OpenStack.
2. What and how much to Standardize (North and South bound APIs)
In the summit, there were several interesting debates on what to standardize and how much. With regards to how much, I am with Guru Parulkar’s mantra to “standardize as little as possible.”
One of the core capabilities that SDN brings to the table is the notion around exposing interfaces from control plane to the infrastructure layer (South Bound APIs or SBI) and to the application/business layer (North bound APIs or NBI). We talked about using common approach for design constructs above, and the APIs are central to the constructs. However, if we (are somehow able to) standardize every hook into the system, we are forcing the industry to take a “single” approach to solve the underlying problems. Additionally, I believe that such an approach will not only go against the very notion of openness, but will also hinder innovation and ability to provide unique experiences.
If we talk about SBI, we rightly need some standardized ways to abstract some of the infrastructure complexities. I learnt that ODL will include support for SDN open standards such as OpenFlow, VxLAN, PCEP etc. Similar to SBI, can we standardize the NBI’s as well?
Read More »
Tags: adoption challenges, APIs, Cisco, Cisco Services, consultative led, opendaylight, OpenStack, SDN, SDN controller