Overview
Understanding Risant Health integration
Who this is for: Medical-surgical, pharmaceutical and equipment suppliers, distributors and revenue-cycle partners that exchange orders, invoices and remittance data with Risant Health.
Scope: This guide describes typical practice for this kind of trading relationship; Risant Health's own program details are confirmed during onboarding.
Risant Health is a Kaiser Permanente-founded nonprofit created to bring independent community health systems into a value-based care model. ECOM's directory lists it under hospital system.
Newly acquired member systems keep many of their own suppliers and payment arrangements during integration. For a health system there are two document families. On the supply side it buys medical, surgical and pharmaceutical products and services and typically handles purchase orders, acknowledgments, ship notices, invoices and inventory data with suppliers and distributors. On the revenue side it receives claim payments and remittance advice from payers (X12 835), which finance teams post to patient accounts. Typical practice keeps these separate and secures patient-related data under healthcare privacy rules.
Risant Health's own EDI or API specification is not part of this guide. What follows is typical practice for hospital system, so confirm the documents, formats, delivery method and testing steps with Risant Health. ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, as software, as a managed service or both.