Tag: Interoperability

Multi-cloud and Modern Applications: Doomed to Fail | Blog

Are multi-cloud and modern applications a panacea or problem? As the cloud journey scales and newer ways of building workloads get adopted, the industry is divided over the value of these initiatives. With increasing concerns about their viability, enterprises need to address some key questions before moving forward. Read on to learn more.   

In our previous blogs, we covered the dichotomy of multi-cloud and explored choice or strategy and interoperability. Let’s now dive into the debate over these approaches.

While enterprises understand the new digital business models require them to fundamentally change the way they consume cloud and build software, they aren’t necessarily aligned on the best models for the future. Not everyone is completely sold on multi-cloud and some doubts by large enterprises are emerging.

The top five questions enterprises ask are:

  1. Is there a better way to solve business challenges than assuming that multi-cloud and modern applications are the panacea?
  2. Is multi-cloud now a distraction to our technology teams?
  3. Is multi-cloud a “fear uncertainty and doubt” created by the nexus of cloud vendors and their partners?
  4. How can we succeed in multi-cloud when we barely have skills for one cloud to build, manage, and optimize workloads?
  5. Why should we build modern applications this way if they are so complex to build, operate, and sustain?

These questions are understandable – even if not always correct. However, unless enterprises become comfortable and address these challenging issues, they cannot proceed in their cloud or modern applications journey.

What should enterprises do?

Based on our research, we recommend the following three steps to succeed:

  • Acknowledge: First, acknowledge that multi-cloud and modern applications are not a cakewalk but very complex strategic initiatives. Moreover, they may not be relevant for all enterprises or use cases. Stress testing the current operating model, development practices, and existing investments are important before charting this journey. In addition, performing analysis to understand the operating cost of multi-cloud and modern applications is critical
  • Assess: Next, discovering existing technology and business estate, aligning with future priorities, and understanding in-house talent, program risks, and funding capabilities become important. Once these decisions are made, enterprises need to consider architectural choices and technology stacks. Wrong choices on these critical input areas can derail the multi-cloud and modern applications journey
  • Act: Finally, understand it is not a foregone conclusion that multi-cloud and modern applications will always benefit or harm your enterprise. In addition to the technology challenges, operating models must change. Therefore, rationalizing tools, realigning teams, prioritizing funnel funding, and transforming talent are critical. Simulating these workloads before they are built and holding cloud vendors and partners contractually accountable is important. Enterprises should also understand that some existing technology investments will be irrelevant, and they will need to buy newer tools across design, build, and run

What should vendors do?

In the complex landscape, cloud providers, service partners, and technology companies have their own incentives and businesses to run, and none have the client’s best interests as their core agenda. Vendors need to build data-driven models to show the value of multi-cloud and modern applications initiatives and help remove as much subjectivity and intuition from this process. Moreover, building platforms that can simulate these workloads across the lifecycle, as well as the talent, funding, and process transformation needed for this journey, are important. If the returns are underwhelming, enterprises should not bother going down the multi-cloud and modern applications route.

Suppliers should be proactive enough to let clients know of the operating model changes needed to adopt multi-cloud and modern applications. We believe system integrators have a more strategic role to play here because cloud or tech vendors do not understand the client landscape and have less incentive to drive such fundamental operating model transformation.

In the end, it boils down to the conviction enterprises have in multi-cloud and modern applications initiatives.  Using tools and platforms to stress test can move the decision from being a gut feeling to fact-based.

Please share your experiences with multi-cloud and modern applications with me at [email protected].

Discover more about our digital transformation research and insights.

Taking the Interoperability and Patient Access Rule beyond Compliance to Capture Its Full Value (Part 3) | Blog

By freeing data from silos, healthcare interoperability can promote greater information exchange between patients, payers, and providers – leading to more efficient care coordination. But compliance with the CMS rule shouldn’t be the only goal. Discover how going beyond what is required can deliver long-term value for enterprises.

Let’s continue our discussion in this final blog in our three-part series where we last explored the types of data shared under the healthcare interoperability rule and how enterprises can navigate through the CMS Interoperability and Patient Access final rule.

While regulatory compliance is critical, it shouldn’t be the sole focus. By investing in the following three areas, healthcare enterprises can create business benefits over time:

  • Master Data Management (MDM): This set of disciplines and solutions helps create and maintain volumes of data from internal and external data sources and applications. It also can enable better decision making by providing a single enterprise view of business-critical data
  • Insight layer (Artificial Learning (AI), Machine Learning (ML), and analytics): While the rule will make health data more accessible, patients and members still will need to understand this raw information. Analytics and AI can help enterprises present the data in simpler formats, deliver insights to patients and members, and make data-driven care decisions
  • Engagement layer (member/patient 360 experience): Currently, members/patients use multiple self-service tools, inadvertently creating a fragmented experience. With Representational State Transfer (REST), Application Programming Interfaces (APIs), Fast Healthcare Interoperability Resources (FHIR), and Health Level 7, enterprises can create a single real-time data view. By leveraging a single data view, enterprises can create a digital front door for members/patients, increasing their comfort and confidence. Also, with a broader data set, healthcare enterprises can direct their engagement initiatives to coordinate care, create Social Determinants of Health (SDoH), match members/patients, and deliver personalized care

Interoperability enablement framework

By better understanding the key components that enable interoperability, enterprises can realize the full benefits it can offer. This framework can enable healthcare enterprises to identify and answer critical questions such as:

  • How do we address scalability and compute challenges?
  • How do we ensure data integration from siloed data sources?
  • Which legacy data needs to be converted into an FHIR format?
  • Which vendors do we engage to build, customize, and maintain FHIR APIs?
  • What assess protocols address security-related functionality such as access management, authorization, and authentication?

The interoperability enablement framework below shows the required IT components for regulatory compliance and what technology features go beyond the regulation:


The interoperability solution landscape

A strong partner ecosystem of technology vendors and service providers can help healthcare enterprises overcome challenges and achieve the long-term benefits of data transparency and delivering a personalized member/patient care experience.

Among the key partner types and offerings to help enterprises enable interoperability are:


What’s next?

We are positive about this regulatory push by the Centers for Medicare & Medicaid Services (CMS) and the Office of the National Coordinator for Health Information Technology (ONC) and view the Interoperability and Patient Access Rule as the first step.

Establishing end-to-end interoperability will require standard data sharing across all systems and devices within the healthcare ecosystem – an essential element for the future of value-based and personalized care.

With the ever-evolving regulatory environment and technology landscape, it will be interesting to watch enterprises adopt these regulations. The required financial investment and technology overhaul will make adoption challenging, but the long-term benefits to all stakeholders can make it rewarding.

Please reach out to [email protected] to share your experiences and ask questions.

How can we engage?

Please let us know how we can help you on your journey.

Contact Us

"*" indicates required fields

Please review our Privacy Notice and check the box below to consent to the use of Personal Data that you provide.