Bring Your EMR. Or Use the One We Built to Connect.
VProGo works with the EMR you have today, including Kipu, Alleva, Sunwave, Opus and CareConnect. It also works with vPro EMR, our own behavioral-health EMR: a separate product, connected to VProGo through an API we own on both sides.
Integration-first, whichever EMR you run
We never tried to replace your EMR. We just built a better-connected one.
VProGo has always run alongside the EMR you already use. That does not change. vPro EMR is simply the option for facilities that want the whole stack from one vendor, or that have no EMR, or are outgrowing a weak one.
Bring your EMR
Keep Kipu, Alleva, Sunwave, Opus or CareConnect. VProGo syncs census, utilization reviews, insurance, and authorization data in real time, so your clinical team keeps the chart they trust and every other role gets a platform built for what they do.
See how integration worksOr use vPro EMR
Run vPro EMR, our behavioral-health EMR. It is a separate system that connects to VProGo through our own API, so admissions, alumni, and the patient app are built to work together. Licensed separately.
Explore vPro EMRAdmissions
Admissions and the chart, connected by an API we own
In any integration, a referral lives in the CRM and the admission lives in the EMR, and data has to move between them. With vPro EMR, both ends of that connection are ours: VProGo and vPro EMR are separate systems built by the same team to work together, and admissions data moves between them through an API we design, maintain, and evolve alongside both products.
- A verification captured at intake surfaces in the chart and in billing without re-entry
- Census and level-of-care transitions flow to VProGo through our own API, not a third-party connector
- Authorization status is shared through the same API
Past the expected arrival, not yet admitted. Reschedule or cancel here, or open the full record.
Alumni
Alumni and aftercare are built in, not bolted on
Discharge is one of the highest-risk transitions in the whole episode, and it is where most systems lose the patient. With vPro EMR, the alumni logic is part of the record: a discharged patient stays in the same connected view, so aftercare is a transition rather than a re-entry, and a former patient who goes quiet is visible to the team that treated them.
- The alumnus stays in the same record as the active patient, not a separate list
- Aftercare and re-engagement are workflows, not a mailing list
- The clinical team keeps line of sight into who is thriving and who has gone quiet
Patient app
One patient app across the whole journey
vPROMove is the patient-facing app the platform already runs on. With vPro EMR, the same app carries the patient from admission through treatment and into alumni. The patient does not switch between a clinical portal and an operations app, and the team sees the responses in one place, because there is only one place.
- The same app from first admission through long-term alumni engagement
- Check-ins and measures feed straight back to the care team, not a separate inbox
- One consistent experience for the patient, one source of truth for the facility
Tap a card or the app's own menu to move through vPROMove.
Tap a feature to see what it does.
Why vPro EMR with VProGo
An integration we own on both sides
An integration we own on both ends
VProGo and vPro EMR are separate systems connected through our own API. When either product changes, the same team updates both sides of the connection.
One patient, end to end
The journey from referral through alumni is designed to line up across both products, instead of across two vendors' data models.
No third-party connector in the middle
With a third-party EMR, the integration depends on that vendor's API and roadmap. With vPro EMR, both sides of the API are ours.
Still integration-first
Prefer to keep Kipu, Alleva, Sunwave, Opus or CareConnect? VProGo still syncs with them in real time. vPro EMR is an option, never a requirement.
Licensed separately
vPro EMR is sold separately from VProGo. Add it when it fits, and work with one team across the clinical record and the operations platform.
One team, two products
Separate products, built to work together
vPro EMR is licensed separately from VProGo. Facilities that add it get a full behavioral-health clinical system of record from the team that builds their operations platform, connected through our own API.
Common questions
Do I have to switch to vPro EMR to use VProGo?
No. VProGo is integration-first and works with the leading behavioral-health EMRs, including Kipu, Alleva, Sunwave, Opus and CareConnect, syncing census, utilization reviews, insurance, and authorization data in real time. vPro EMR is an option for facilities that want the whole stack from one vendor, or that have no EMR or are outgrowing a weak one. You are never required to switch.
What makes vPro EMR different from integrating my existing EMR?
vPro EMR and VProGo are separate systems, connected through an API we build and own on both sides. With a third-party EMR, the integration depends on that vendor's API and roadmap. With vPro EMR, both ends of the connection are ours, so admissions, alumni, and patient-app data are designed to line up, and the integration evolves with both products.
How much does vPro EMR cost?
vPro EMR is licensed separately from VProGo, for an additional fee. Talk to sales for pricing for your facility.
Is vPro EMR a full behavioral-health EMR?
Yes. vPro EMR is a complete behavioral-health EMR and clinical system of record, built for the way treatment centers actually document and deliver care, and connected to the VProGo operations platform through our own API.
What is the shared patient app?
vPROMove is the patient-facing app used across the VProGo platform. With vPro EMR, the same app carries the patient from admission through treatment and into alumni, so the patient never switches between a clinical app and an operations app.
See the full vPro EMR
vPro EMR has its own home, with the clinical detail, the feature walkthroughs, and the screens in full.
Visit vproemr.com