# Transforming Healthcare: The Role of Open and Flexible Care Management Systems (HealthEdge)
## Key facts
- **3 “must-haves”** define modern care management systems: (1) access and share a variety of data across the IT ecosystem, (2) accommodate **real-time data exchange**, and (3) be **open** and able to work seamlessly with other software systems (Section: “Care Management Must-Haves,” list of three criteria).
- Clinical Edge (formerly **GuidingCare®**) was “one of the first” care management solutions to deploy **FHIR-based APIs** as CMS announced its intention to make this the new standard for data sharing (Section: “The system must be able to access and share a variety of data across the IT ecosystem,” para beginning “Modern care management systems…”).
- Clinical Edge supports **API-based integrations** for real-time data sharing via **RESTful APIs** and **JSON payloads** (Section: “sharing data in real time takes care-planning to the next level,” para beginning “Modern care management systems…”).
- Health plans may have **up to 25 different systems** in their ecosystem that must work together to optimize member health and wellness (Section: “The system must be open and capable of working seamlessly with other software systems,” para beginning “Care management systems sit at the core…”).
- Clinical Edge works with **more than 75 unique external vendors via APIs**, supporting data categories including “more accurate claims, better risk scoring, and more real-time member and provider collaboration” (Section: “The HealthEdge Difference,” para beginning “In fact, to date…”).
- The document cites specific regulatory pressure including the **21st Century Cures Act** and market shifts such as **value-based care** as drivers for more nimble, adaptable health plan IT (Section: opening context on transformational change, bullet list).
## Summary
### Why health plans need more nimble care management systems
Today’s healthcare market is described as “rapidly changing,” pushing health plans to become more adaptable due to factors such as evolving regulatory requirements (including the **21st Century Cures Act**), emerging payment models like **value-based care**, new sources and types of data, rising consumer expectations, and new opportunities for geographic and line-of-business expansion (Section: opening context, transformational change bullets). The paper argues that many health plans are held back by monolithic care management systems that require lengthy, complex implementations and significant IT involvement, along with gaps in accessing and exchanging real-time data (Section: opening context, paragraphs on monolithic systems and real-time data gaps).
### What “modern” care management must include (3 must-haves)
The paper outlines **three primary criteria** for modern care management systems: the ability to access and share data across the IT ecosystem, support real-time data exchange, and remain open so the system can work seamlessly with other software (Section: “Care Management Must-Haves,” list). It emphasizes that relevant clinical data can come from many sources—ranging from a provider EHR (electronic health record) to a member’s Apple Watch—and includes non-traditional inputs like **social determinants of health (SDOH)** data and claims data for identifying risk (Section: “The system must be able to access and share…,” paragraphs on data sources).
### How interoperability and composable architectures are positioned
Interoperability is framed as valuable for both vendors and health plans: vendors can automate more processes with timely and accurate data, while health plans can gain better insight for decisions and avoid data being locked in specific systems (Section: “Why Is Interoperability So Important?”). The paper also argues that “no single system can do it all,” noting organizations may have **up to 25 different systems**, and that lack of seamless integration can create manual workarounds and IT overhead (Section: “The system must be open…,” para beginning “But in today’s complex healthcare environment…”).
Clinical Edge (formerly **GuidingCare®**) is presented as an example of a system designed for interoperability and composability, including support for **FHIR-based APIs** and real-time sharing through **RESTful APIs** and **JSON payloads** (Sections: data-sharing discussion and real-time exchange discussion). It also states that Clinical Edge works with **more than 75 unique external vendors via APIs** (Section: “The HealthEdge Difference”). The paper includes attributed perspectives from **Christopher D. Palmieri** (Commonwealth Care Alliance) on configurable options and reporting/analytics, and from **David Kaercher** (CareFirst, Executive Vice President & CIO) on using **FHIR API** support to accelerate technical consolidation and data integration efforts (Sections: quote blocks under “The system must be open…” and later quote under “Our objective…”).