Now in production with VRepro clinics.See the integration

VRepro integration

The data and automation layer for VRepro clinics.

VRepro runs your clinic and your lab. Nidus connects it to everything else, with a production connector that reads and writes patients, episodes and documents, and reaches even on-premise deployments. No migration, no rip-and-replace.

A production VRepro connector, not a promise.

Nidus already speaks VRepro in production for a live fertility clinic. Here is what that connector does.

Two-way sync

Read and write patients, episodes and documents. Keep VRepro in step with your CRM, lab and billing without anyone re-keying data.

Reaches on-premise VRepro

VRepro often accepts calls only from a whitelisted clinic host. An outbound-only agent runs there and executes calls locally, so the clinic opens no inbound port.

Credentials stay on site

The agent can hold VRepro credentials locally and Nidus never stores them centrally. Your most sensitive data never leaves the building.

No migration

VRepro stays your system of record. Nidus sits on top and makes it cooperate with everything else you run.

The on-premise agent

Cloud reach, on-premise trust.

A lightweight agent runs on the whitelisted clinic host. It dials out to Nidus, receives jobs, and runs them against VRepro locally, then posts the results back. The clinic changes no firewall rules, and the patient data executes on premise.

Nidus (cloud)

↓ job: create patient

Agent (clinic host, whitelisted)

→ VRepro on premise

← result

Nidus updates the journey

Outbound only. No inbound port opened at the clinic.

Workflows that run on top of VRepro.

Once VRepro is connected, put its data to work across the systems your teams live in.

Consent on qualification

When a lead qualifies in the CRM, send the right consent documents for signature.

Signed documents to VRepro

File completed signature envelopes against the correct patient record.

Appointments and budgets to CRM

Surface VRepro appointments, budgets and treatments in the CRM for the front office.

Failed-cycle follow-up

When a cycle is registered as failed, open a follow-up task with an owner and an SLA.

Put your VRepro data to work.

We connect VRepro to your CRM, lab and billing, and prove one workflow on your own data first.