Juli 2019 - Seite 5 von 82 - Cloud Computing Köln

The healthcare industry is at a turning point. Patients and providers are eager for advances in value-based care, patient engagement, and machine learning as they look to usher in a new era of constantly-improving health outcomes and well-being. Interoperability is key to removing the barriers between the healthcare industry and the future it seeks to build.Having a strong and continued commitment to data interoperability will offer faster data insights to improve patient outcomes, increase productivity, and reduce physician burnout. Our commitment to interoperability involves investment in our own products like theCloud Healthcare API, as well as our contributions to the open source tools including Google’s FHIR protocol buffers andApigee Health APIx, which will help developers embrace and implement these standards with ease.We believe it is important to work with stakeholders across the ecosystem – patients, providers, insurers, researchers ,tech providers – to unlock important data and enable patients and their care teams to derive insights when it is needed most. Today, we are very proud to announce that Google Cloud is joined with Amazon, IBM, Microsoft, Oracle, and Salesforce in support of healthcare interoperability with the following statement at theBlue Button 2.0 Developer Conference at the White House.Full statement below: As healthcare evolves across the globe, so does our ability to improve the health and wellness of communities. Patients, providers, and health plans are striving for more value-based care, more engaging user experiences, and broader application of machine learning to assist clinicians in diagnosis and patient care.Too often, however, patient data are inconsistently formatted, incomplete, unavailable, or missing—which can limit access to the best possible care. Equipping patients and caregivers with information and insights derived from raw data has the potential to yield significantly better outcomes. But without a robust network of clinical information, even the best people and technology may not reach their potential.Interoperability requires the ability to share clinical information across systems, networks, and care providers. Barriers to data interoperability sit at the core of many process problems. We believe that better interoperability will unlock improvements in individual and population-level coordination, care delivery, and management. As such, we support efforts from ONC and CMS to champion greater interoperability and patient access.This year’s proposed rules focus on the use of HL7® FHIR® (Fast Healthcare Interoperability Resources) as an open standard for electronically exchanging healthcare information. FHIR builds on concepts and best-practices from other standards to define a comprehensive, secure, and semantically-extensible specification for interoperability. The FHIR community features multidisciplinary collaboration and public channels where developers interact and contribute. We’ve been excited to use and contribute to many FHIR-focused, multi-language tools that work to solve real-world implementation challenges. We are especially proud to highlight a set of open-source tools including: Google’s FHIR protocol buffers and, Microsoft’s FHIR Server for Azure, Cerner’s FHIR integration for Apache Spark, a serverless reference architecture for FHIR APIs on AWS, Salesforce/Mulesoft’s Catalyst Accelerator for Healthcare templates, and IBM’s Apache Spark service.Beyond the production of new tools, we have also proudly participated in developing new specifications including the Bulk Data $export operation (and recent work on an $import operation), subscriptions, and analytical SQL projections. All of these capabilities demonstrate the strength and adaptability of the FHIR specification. Moreover, through connectathons, community events, and developer conferences, our engineering teams are committed to the continued improvement of the FHIR ecosystem. Our engineering organizations have previously supported the maturation of standards in other fields and we believe FHIR version R4—a normative release—provides an essential and appropriate target for ongoing investments in interoperability. We have seen the early promise of standards-based APIs from market-leading Health IT systems, and are excited about a future where such capabilities are universal. Together, we operate some of the largest technical infrastructure across the globe serving many healthcare and non-healthcare systems alike. Through that experience, we recognize the scale and complexity of the task at hand. We believe that the techniques required to meet the objectives of ONC and CMS are available today and can be delivered cost-effectively with well-engineered systems.At Amazon, Google, IBM, Microsoft, Oracle, and Salesforce, we are fortunate to work with many teams and partners that draw on experiences across industries to support and accelerate the delivery of FHIR APIs in healthcare. Moreover, we are committed to introducing tools for the healthcare developer community. After the proposed rule takes effect, we commit to offering technical guidance based on our work including solution architecture diagrams, system narratives, and reference implementations to accelerate deployments for all industry stakeholders. We will work diligently to ensure these blueprints provide a clear and robust path to achieving the spirit of an API-first strategy for healthcare interoperability. As a technology community, we believe that a forward-thinking API strategy as outlined in the proposed rules will advance the ability for all organizations to build and deploy novel applications to the benefit of patients, care providers, and administrators alike. ONC and CMS’s continued leadership, thoughtful rules, and embrace of open standards help move us decisively in that direction.Signed,Amazon, Google, IBM, Microsoft, Oracle, and Salesforce
Quelle: Google Cloud Platform

31. Juli 2019

da Agency

Cloud providers unite on frictionless health data exchange

This post was co-authored by Heather Jordan Cartwright, General Manager, Microsoft Healthcare

Cloud computing is rapidly becoming a bigger and more central part of the infrastructure of healthcare. We see this as a historic shift that motivates us to think hard about how to ensure that, in this cloud-based future, interoperable health data is available as needed and without friction.

Microsoft continues to build health data interoperability into the core of the Azure cloud, empowering developers and partners to easily build data-rich health apps with the Azure API for FHIR®. We are also actively contributing to healthcare community with open source software like the FHIR Server for Azure, bringing together developers on collaborative solutions that move the industry forward.

We take interoperability seriously. At last summer’s CMS Blue Button Developer Conference, we made a public commitment to promote the frictionless exchange of health data with our counterparts at AWS, Google, IBM, Salesforce and Oracle. That commitment remains strong.

Today, at the same conference of health IT community leaders, we are sharing a joint announcement that showcases how we have moved from principles and commitment to actions. Our activities over the past year include open-source software releases, development of new standards and implementation guides, and deployment of services that support U.S. federal interoperability mandates.

Here’s the full text of our joint announcement:

As healthcare evolves across the globe, so does our ability to improve the health and wellness of communities. Patients, providers, and health plans are striving for more value-based care, more engaging user experiences, and broader application of machine learning to assist clinicians in diagnosis and patient care.

Too often, however, patient data are inconsistently formatted, incomplete, unavailable, or missing – which can limit access to the best possible care. Equipping patients and caregivers with information and insights derived from raw data has the potential to yield significantly better outcomes. But without a robust network of clinical information, even the best people and technology may not reach their potential.

Interoperability requires the ability to share clinical information across systems, networks, and care providers. Barriers to data interoperability sit at the core of many process problems. We believe that better interoperability will unlock improvements in individual and population-level care coordination, delivery, and management. As such, we support efforts from ONC and CMS to champion greater interoperability and patient access.

This year's proposed rules focus on the use of HL7® FHIR® (Fast Healthcare Interoperability Resources) as an open standard for electronically exchanging healthcare information. FHIR builds on concepts and best-practices from other standards to define a comprehensive, secure, and semantically-extensible specification for interoperability. The FHIR community features multidisciplinary collaboration and public channels where developers interact and contribute.

We’ve been excited to use and contribute to many FHIR-focused, multi-language tools that work to solve real-world implementation challenges. We are especially proud to highlight a set of open-source tools including: Google’s FHIR protocol buffers and Apigee Health APIx, Microsoft’s FHIR Server for Azure, Cerner's FHIR integration for Apache Spark, a serverless reference architecture for FHIR APIs on AWS, Salesforce/Mulesoft's Catalyst Accelerator for Healthcare templates, and IBM’s Apache Spark service.

Beyond the production of new tools, we have also proudly participated in developing new specifications including the Bulk Data $export operation (and recent work on an $import operation), Subscriptions, and analytical SQL projections. All of these capabilities demonstrate the strength and adaptability of the FHIR specification. Moreover, through connectathons, community events, and developer conferences, our engineering teams are committed to the continued improvement of the FHIR ecosystem. Our engineering organizations have previously supported the maturation of standards in other fields and we believe FHIR version R4 — a normative release — provides an essential and appropriate target for ongoing investments in interoperability.

We have seen the early promise of standards-based APIs from market leading Health IT systems, and are excited about a future where such capabilities are universal. Together, we operate some of the largest technical infrastructure across the globe serving many healthcare and non-healthcare systems alike. Through that experience, we recognize the scale and complexity of the task at hand. We believe that the techniques required to meet the objectives of ONC and CMS are available today and can be delivered cost-effectively with well-engineered systems.

As a technology community, we believe that a forward-thinking API strategy as outlined in the proposed rules will advance the ability for all organizations to build and deploy novel applications to the benefit of patients, care providers, and administrators alike. ONC and CMS’s continued leadership, thoughtful rules, and embrace of open standards help move us decisively in that direction.

Signed,
Amazon, Google, IBM, Microsoft, Oracle, and Salesforce

The positive collaboration on open FHIR standards and the urgency for data interoperability have strengthened our commitment to an open-source-first approach in healthcare technology. We continue to incorporate feedback from the community to develop new features, and are actively identifying new places where open source software can help accelerate interoperability.

Support from the ONC and CMS in 2019 to adopt FHIR APIs as a foundation for clinical data interoperability will have a profound and positive effect on the industry. Looking forward, the application of FHIR to healthcare financial data including claims, explanation of benefit, insurance coverage, and network participation will continue to accelerate interoperability at scale and open new pathways for machine learning.

While it’s still early, we’ve seen our partners leveraging FHIR to better coordinate care, to develop innovative global health tracking systems for super-bacteria, and to proactively prevent the need for patients undergoing chemotherapy to be admitted to the emergency room. FHIR is providing a foundational platform on which our partners can drive rapid innovation, and it inspires us to work even harder to deliver technology that makes interoperable data a reality.

We’re just beginning to see what is possible in this new world of frictionless health data exchange, and we’d love for you to join us. If you want to participate, comment or learn more about FHIR, you can reach our FHIR Community chat here.
Quelle: Azure

30. Juli 2019

da Agency

How AIOps can drive performance

Imagine your IT applications, services and infrastructures running like a high-performing Formula 1 race car — with its engine and gears running smoothly as the driver accelerates through the straights and decelerates while its tires and suspension hug the track through the curves.
However, even when the race is running smoothly, obstacles arise, track conditions change, engine parts overheat, or tires and suspension parts give out.
So professional world class racing teams — much like teams managing and operating highly complex IT systems, applications and services — are constantly managing unexpected situations and issues that can become very expensive if not handled quickly and intelligently.
Even if your team has the most advanced engineering, conducts the most professional and experienced planning, and drives the most attentive operations management in production, you’re unlikely to avoid the unexpected.
Successful IT operations management teams, just like winning racing teams, know that the challenge is not “if” service-impacting incidents occur, but “when”.
Once you expect the unexpected, imagine what your team must do to react with agility. You can work towards operating more proactively to ultimately minimize or prevent them. How would you better anticipate, prepare for and improve responsiveness? How would you automate problem triage, investigation and resolution activity when incidents occur?
How AIOps helps teams operate more intelligently, proactively and flexibly
Whether you’re running a world-class racing team, or a world-class IT operations team, imperatives for success include the following:
1. Navigate through the noise.
Imagine if your company had a way to navigate and cut through alarm noise in an automated way, regardless of the type of workload, environment or tool generating the alarm. Instead of getting inundated with notifications for every monitoring threshold crossed, teams are notified only when specific service level parameters are met. Any and all related events are grouped together in context into an incident that is easy to consume, understand, share and take action on.
2. Investigate and take corrective action faster.
The key to making good decisions and taking action is confidence. Your team’s confidence gets a turbo boost when they are immediately and continuously empowered with critical and relevant data and contextual information to quickly assess what’s happening, what is being impacted, and receive guidance with automated steps to resolve the problem. Operating more intelligently will help get your business back on the track and running smoothly with fewer pitstops.
3. Get ahead of the curve.
It’s imperative to react to problems when they flare up, but to reduce ongoing operational expenses (OPEX) and gain efficiency, teams must operate more proactively. Imagine if you could prepare your teams ahead of time with automated steps to quickly restore service when problems occur and empower team members of any skill set to take action with confidence. This was the case for Nextel, a leading service provider in Brazil.
4. Use the past to fix the present and predict the future.
Imagine if your company had an early warning detection system that alerted teams when current conditions were actually indicators of worsening problems that are likely to occur. When a high-performance race car has low tire pressure, low fuel levels, or high engine temperature, it’s not a big leap to predict that a spin out or burn out is likely to occur if these issues are left unattended.
In highly complex, dynamically changing IT production environments it’s not so easy. But if you can see a trend line of incident activity, identify where similar smaller, less urgent indicators led to more severe problems in the past, and get a prediction of those potential problems before they impact apps and services, it can be simpler to avoid costly outages and slow-downs.
Continuous machine learning improves and fine tunes operations over time. To do so, analysis and curated information is needed that warns you when likely problems are building and what could be done to prevent or at least mitigate it.
Operating proactively is intended to keep you on the track and avoiding unnecessary pitstops altogether.
5. Deploy and operate to current needs, and easily adapt to changes later.
Even the best racing strategies and plans can change. Some obvious factors such as weather conditions, driver resilience and pole position can disrupt even the best plans.
Operations teams are challenged with stakeholder demands to run on new platforms, shift workloads to different environments or make continuous updates requiring significant adjustments to support functions and procedures. Management tools help control these disruptions, providing they are flexible enough to allow you to deploy in the manner and on the platform(s) you need them to, and easily change as you adopt more modern platforms — all without causing extra transition pain or disruption.
Operating with flexibility is like ensuring all the necessary spares for your high-performance vehicle are readily available and ready to fit without customization.
How to ensure the right AIOps tools under the hood
Like any world-class racing team, IT operations management teams rely on market-proven, time-tested and high-performance tools to keep their businesses running at the highest level.
The latest version of the industry leading IBM Netcool Operations Insight (v1.6) rises to that challenge, with new significant AIOps capabilities under the hood that help enable teams to respond intelligently and quickly when service-impacting problems inevitably happen. The solution can also help you observe what teams do to investigate, diagnose and resolve problems, plus observe performance and incident trends, to then learn what’s working and what can be improved proactively.
Learn how Netcool Operations Insight can support your high performance ITOps and DevOps teams with the latest in AIOps tools and capabilities to be more intelligent, proactive and flexible. Then check out the five concrete steps you can take in moving from ITOps to AIOps, and get ready to embrace the operations challenges of your next race.
The post How AIOps can drive performance appeared first on Cloud computing news.
Quelle: Thoughts on Cloud