# Clinical Edge API Catalog 2026: API Integration Suite for Payer IT Ecosystems
## Key Facts
- **2026**: The *Clinical Edge API Catalog 2026* describes **Clinical Edge (formerly GuidingCare®)** and its **API Integration Suite** designed to connect external solutions across the payer IT ecosystem. (Clinical Edge API Catalog 2026, intro section)
- **7 API categories** are listed: **Member Services**, **Authorization Services**, **Assessments Services**, **Service Plan Services**, **Complaint Services**, **Query Services**, and **Workflow Management Services**. (Section: “Clinical Edge API Categories”)
- **RESTful APIs**: Clinical Edge “utilizes **RESTful APIs** to retrieve and update data in real time,” and “all services within the Integration API Suite follow clinical workflow rules” built into Clinical Edge. (Intro section)
- **Member Services APIs** include capabilities such as verifying eligibility/benefit coverage, managing consent forms and advance directives, retrieving health indicators/allergies, entering medications, retrieving appointments and **social determinants of health (SDOH) referrals**, and managing documents/health notes. (Section: “Member Services”)
- **Authorization Services APIs** include automating authorization decisions for procedures that meet medical necessity, automating follow-ups after admissions, routing authorizations requiring physician reviews to the right work queue, and notifying members/providers of approvals and denials. (Section: “Authorization Services”)
- **Workflow Management Services APIs** include automatically creating tasks and assigning them to care staff or external care team members (such as a PCP), and alerting care staff to changes like ER visits or hospital admission. (Section: “Workflow Management Services”)
## Summary
### What the Clinical Edge API Catalog 2026 Covers
The *Clinical Edge API Catalog 2026* outlines how **Clinical Edge (formerly GuidingCare®)** supports interoperability across the payer IT ecosystem through a **robust API Integration Suite**. It states that the platform uses **RESTful APIs** to retrieve and update data **in real time**, and that services in the Integration API Suite follow **clinical workflow rules** built into Clinical Edge. (Intro section)
### API Categories and What They Enable
The catalog groups Clinical Edge APIs into **7 categories**: **Member Services**, **Authorization Services**, **Assessments Services**, **Service Plan Services**, **Complaint Services**, **Query Services**, and **Workflow Management Services**. (Section: “Clinical Edge API Categories”)
Across these categories, the document highlights use cases such as eligibility and benefit coverage verification; authorization workflows (including medical necessity, automation, and physician review routing); assessment and survey workflows (including templates, submissions, prior answers, and dynamic fields); service plan visibility and acknowledgments/denials; complaint and appeals processing with routing, attachments, and notifications; code/provider search and claim detail retrieval; and workflow task creation and alerts tied to member record changes. (Sections: “Member Services,” “Authorization Services,” “Assessment Services,” “Service Plan Services,” “Complaint Services,” “Query Services,” “Workflow Management Services”)
### Where to Find Technical Specifications
For deeper implementation detail, the catalog directs readers to the **Developer Portal** for “API specifications and technical documentation.” (Section: “Workflow Management Services,” closing note)