Founded: Kicked off in 2017

HQ: Pittsburgh, PA

An API-driven platform that makes health care data available to authorized applications and streamlines technology development.

Health care is in need of a technology infrastructure where data, both historical and real-time, is readily available to providers, consumers, and payers.

To address this need, UPMC is both creating and adopting the cloud-based health care operating system, or hcOS, in order to aggregate, index, and provision access to data. The ultimate goal of hcOS is to provide both a platform and tools for developers in health care that can foster an ecosystem of third-party apps working on top of legacy IT systems.

hcOS begins to address three major issues in health care today:

Siloed Data

Siloed Data

Critical clinical and financial data is held in many different systems that don’t communicate; as the industry consolidates, this problem is only becoming more daunting.

Vendor lock in

Vendor Lock-In

Providers often may rely on multiple vendor solutions for their digital record systems, and those vendors have no incentive to make it easy to share data between these systems.

Innovation velocity

Weak "Innovation Velocity"

Health care traditionally moves very slowly when it comes to implementing new technology and systems.

Without a common set of tools to perform standard tasks, a developer would have to build their own tools and anything else that is required to connect an app to the broader IT and data systems.

There are roughly 300,000 mobile health apps today, only a very few of which are integrated with existing EMR systems. To date, the health care industry has failed to develop a robust third-party developer ecosystem.

Given the goals and constraints, the most viable solution is to build a software platform that is layered on top of these existing health care IT systems, creating a developer ecosystem to spur development and innovation.

Below is a visual snapshot of hcOS. The middle or green layer, is where UPMC Enterprises is focusing much of its current work. This layer involves independent components organized into four categories: Data Platform (HDP), Tools, Processing and APIs. The bottom, or purple, layer represents the various source systems a health system may have. And the top, or blue, layer represents various applications that can access data in hcOS.

hcOS overview

To date, UPMC has used hcOS components for success in government-sponsored, value-based care models as well as several other use cases throughout the system.

To learn more about hcOS and discuss implementation use-cases with our team, contact us.