VProGo

Getting your facility ready…

VProGo + Kipu

Kipu runs your chart.
VProGo runs everything else.

Kipu is the market-leading behavioral health EMR — your clinicians know it, your audits depend on it, and you're not about to replace it. VProGo bidirectionally syncs with Kipu and runs the operations layer it was never built to be: referrals, prediction, billing, patient engagement, multi-facility roll-up.

What lives where

The complementary split, grounded in our shipping Kipu integration (`lib/kipu/`) and Kipu's public product surface. The chart stays in Kipu — operations land in VProGo.

Clinical documentation, charting, eMAR, utilization review
Kipu owns the chart and the clinical workflow. We don't try to compete — we sync into it.
VProGo
Kipu
Census + bed management (real-time, bidirectional)
Both sides see the same census. Kipu writes the chart; VProGo gives you the portfolio view across facilities.
VProGo
Kipu
Multi-facility roll-up + portfolio dashboards
Kipu's UI is single-facility-first. VProGo is built for the multi-facility operator from day one.
VProGo
Kipu
Bidirectional clearinghouse (Claim.MD / CollaborateMD / Waystar)
Kipu has Avea billing (residential-focused). VProGo's clearinghouse layer is native and multi-payer.
VProGo
Kipu
RM Hub three-tier drill (KPI → claim → clinical evidence)
Tie revenue metrics back to the chart event that justifies them. Same patient, same dollar, two clicks apart.
VProGo
Kipu
Patient-facing mobile app (recovery + alumni)
vProMove gives patients in-program goals and alumni community after discharge. Drives readmission attribution and reviews.
VProGo
Kipu
Inbound + outbound referral pipeline + partner attribution
Kipu has light intake tracking. VProGo runs the full BD funnel with per-partner P&L.
VProGo
Kipu
Live call attribution (CTM / CallRail / RingCentral)
Calls flow into referrals, into admissions, into paid claims. End-to-end campaign-to-claim attribution.
VProGo
Kipu
8-tier payment prediction engine (vPro Predict)
Confidence-tier reimbursement projections before you confirm the bed — not after the EOB lands.
VProGo
Kipu
Embedded SEO + marketing intelligence (VProSEO)
Marketing operations in the platform, not on a separate vendor stack. CRM Bridge ties keywords to admissions.
VProGo
Kipu
AI Pulse briefing across census / referrals / billing
One daily digest surfaces what changed overnight and what's about to slip. Cross-surface, not per-module.
VProGo
Kipu
Plug-and-play deployment alongside existing Kipu
Goes live without disrupting your clinical floor. Your clinicians never leave Kipu.
VProGo
Kipu

= partial / add-on / requires a third-party tool ·= not in current product surface as of 2026-05.

How the integration works in practice

Three concrete things that happen after the Kipu sync goes live, every one grounded in shipping code.

Bidirectional, with the chart as source of truth

Admissions, demographics, census, level-of-care transitions, insurance, authorizations, group attendance, and discharges sync between Kipu and VProGo via the native API. Clinical notes stay in Kipu — only the operational data needed to run referrals, billing, and engagement flows out. Migration `20260517170000` enforces LIST → DETAIL sidecar so no Kipu sync gap goes undetected.

Unsigned notes become action items, not stale counts

Kipu attendance and signature data flows into VProGo's compliance gate (`get_attendance_compliance`). Operators see a ranked list of action items — not a counter showing 'X unsigned notes' that includes absent patients and sync-gap days. The compliance fire stops being a fire.

Discharges trigger vProMove the same day

When Kipu fires a discharge event, vProMove enrollment runs automatically. Recovery check-ins, journaling, and message threads with the alumni coordinator start the day the patient leaves treatment — not weeks later when someone in marketing remembers to import the list.

See the Kipu + VProGo stack

30-minute demo. We'll walk through the integration on a real Kipu-connected facility, show you the data flow both directions, and demonstrate what VProGo layers on top.