Integration, VRepro
Nidus integration with VRepro
VRepro covers the clinical and laboratory cycle, including the traceability of cryopreserved samples. Nidus connects that information to the CRM, e-signature and billing, and VRepro remains the system of record.
read and write, kept in sync both ways
What the integration covers
VRepro holds the clinical and laboratory information. Commercial activity, document signature and accounting sit in other systems. Nidus links both sides, in both directions.
Two-way sync
Patients, episodes and documents are read and written in both directions. VRepro stays aligned with the CRM, the laboratory and billing without re-entering data.
VRepro installed at the clinic
VRepro often accepts connections only from an authorised host at the clinic. An agent runs on that host and executes the operations locally, so the clinic opens no inbound access.
Credentials stay at the clinic
The agent can hold the VRepro credentials locally. Nidus does not store them centrally.
No migration
VRepro remains the system of record. Nidus works on top of it and connects it to the other systems.
The local agent
Connection to VRepro installed at the clinic
A lightweight agent runs on the authorised host at the clinic. It connects out to Nidus, receives the operations, runs them against VRepro locally and returns the results. The clinic changes no firewall rules, and patient data is processed on premise.
Nidus (cloud)
↓ job: create patient
Agent (authorised host at the clinic)
→ VRepro at the clinic
← result
Nidus updates the journey
Outbound only. No inbound port opened at the clinic.
Workflows on VRepro data
Once VRepro is connected, its data is used in the other systems of the clinic.
Consent on qualification
When a contact qualifies in the CRM, the corresponding consent documents are sent for signature.
Signed documents to VRepro
Signed documents are filed in the corresponding patient record.
Appointments and budgets to the CRM
VRepro appointments, budgets and treatments are shown in the CRM for the patient-care team.
Failed-cycle follow-up
When a cycle is recorded as failed, a follow-up task is opened with an owner and a deadline.
See Nidus in operation
Book a full demo of the platform: the data model, the cockpit, the workflows and the integration process.