The fertility data platform
Stop losing patients in the gaps between your systems.
Nidus connects the CRM, EMR, lab, billing and patient apps your fertility clinic already runs, VRepro included, into one data model with automated workflows and full visibility over every record that moves.
- One data layer
- across every system you run
- Zero migration
- VRepro stays your system of record
- On-premise reach
- data stays in the clinic
Patient journey visibility
Exception queue
- Missing admin docs27 patients· Admin4h SLA
- Payment not confirmed18 patients· Finance2h SLA
- Medical tests overdue11 patients· Clinical6h SLA
Ask Nidus
Why did 42 patients stall this week?
Top drivers
- Missing documents
- No assigned owner
- Deposit unpaid
Connects the systems fertility clinics already run
Fragmented systems quietly cost you patients.
Fertility clinics run on specialised tools that were never built to talk to each other. The cost shows up as churn, duplicated work and revenue no one can trace.
Patients slip between systems
A lead qualified in the CRM never gets created in the EMR. A signed consent never reaches the lab. No one sees the gap until the patient is gone.
Everything is entered twice
Staff re-key the same patient into VRepro, the CRM and billing. Duplicates, errors and hours lost to work the systems should do themselves.
No one sees the whole journey
Each system holds a fragment. There is no single view of where patients stall, which handoffs fail, or where revenue quietly leaks.
Rip-and-replace is not an option
Your EMR runs the clinic and the lab. You need your systems to cooperate, not a risky migration that halts operations.
A data platform built for fertility, not a generic integration bus.
Nidus is deliberately layered: a semantic core that ingests every system, a cockpit for full visibility, and a catalogue of workflows that act on the data.
nidus core
A fertility-specific data model and plug-and-play connectors that translate every system into shared concepts: Person, Cycle, Episode, Embryo.
nidus cockpit
One interface for the clinic or group: connection status, the patient journey with leakage, an exception queue with SLAs, and analytics in plain language.
nidus workflows
A catalogue of automations that act across systems: assign an owner, open a task, start an SLA, or update another system the moment something changes.
Built for VRepro clinics
Already running VRepro? Nidus speaks it natively.
VRepro runs your clinic and your lab, and we do not ask you to replace it. Nidus ships a production VRepro connector that reads and writes patients, episodes and documents, and reaches even IP-whitelisted, on-premise deployments through a secure outbound-only agent. Your patient data and credentials stay inside the clinic.
- → Two-way sync between VRepro and your CRM, lab and billing
- → Reaches on-premise VRepro without opening the network
- → No migration. VRepro stays your system of record
28+
countries across four continents where VRepro is deployed.
Nidus is built to be the data and automation layer on top of the fertility software clinics already trust, starting with the EMRs that run the lab.
Deployment figure per NaturalSoft, VRepro's vendor.
Connectors
Connect the systems your clinic already runs.
A growing set of connectors is live in production. New connectors are built with design partners, prioritised by repeatability and economic pain.
One platform, value on both sides of the group.
Leadership gets visibility and a repeatable standard. The clinic floor gets fewer duplicates and patients that do not stall. Same platform, same data model.
For the group
Owners, group CTO and COO
- Cross-group visibility on one shared data model
- One operating standard, rolled out site by site
- Growth without ripping out the EMR
- Analytics you can ask in plain language
For the clinic floor
Operations, front office and lab
- No double data entry across systems
- Patients stop stalling between CRM, EMR and lab
- An exception queue, owned and time-boxed by SLA
- Everything inside the tools your teams already use
One platform, every building block.
Connectors, two-way sync, workflows, the cockpit and managed sync with MCP access. Each piece works on its own, and together they keep your clinic's systems in agreement.
Connect the systems you already run.
In sync, both ways.
If this, then that.
See the whole journey.
active · orphan-risk · SLA met
We run it. Agents can query it.
If something happens here, act there.
Workflows watch for a signal in one system, apply a rule, and take action in another: assign an owner, open a task, start an SLA, or update a record. Organised in families you switch on per clinic.
If, System A
Event, condition, context
A cycle is registered as failed in the EMR.
Nidus rule
Evaluate, prioritise, route
Decide it needs follow-up, set the owner and the deadline.
Then, System B
Assign, alert, queue, SLA
Create a follow-up task with an owner and an SLA in the CRM.
Example. Failed-cycle follow-up: nothing falls through, and the patient is contacted in time.
Person, Couple, Cycle, Episode, Embryo. Not rows in ten databases.
Nidus core translates fragmented clinic data into shared fertility concepts that can be reused across every system and workflow, with a governance layer for data quality, lineage and multi-tenant security.
Security & compliance
Health data, handled to enterprise standard.
Fertility data is special-category personal data. Nidus is built privacy-first, so security is a foundation, not a bolt-on.
- Multi-tenant with row-level security, so you only ever see your own data
- Write-only credentials, stored in a secrets vault, never rendered back
- On-premise egress agent: data and credentials stay inside the clinic
- Append-only audit log and data-retention controls
- EU data residency for EU clinics
- Built toward ISO 27001, ISO 27701 and SOC 2
Plans that scale with your group.
Every plan includes the Nidus core data model. Licensing is per site and scales with the connectors and workflows you turn on. Talk to sales for a quote tailored to your group.
Starter
Land your first connected workflows.
- ✓ Nidus core data model
- ✓ 4 connectors
- ✓ 10 workflows
Growth
Scale automation across sites.
- ✓ Nidus core data model
- ✓ 8 connectors
- ✓ 30 workflows
- ✓ No-code Workflow Creator
- ✓ Multi-site
Enterprise
Group-wide coverage and governance.
- ✓ Nidus core data model
- ✓ 15 connectors
- ✓ 70 workflows
- ✓ No-code Workflow Creator
- ✓ Group rollout & governance
Sources: Adamson et al. (2023); Grand View Research, ART Market 2024 to 2030.
Frequently asked questions
- Do we have to replace our EMR or VRepro?
- No. Nidus sits on top of the systems you already run and makes them cooperate. There is no rip-and-replace: your EMR keeps running the clinic while Nidus keeps every other system in sync with it.
- We run VRepro. Does Nidus work with it?
- Yes. Nidus ships a production VRepro connector that reads and writes patients, episodes and documents. It reaches even IP-whitelisted, on-premise deployments through a secure outbound-only agent, so your data and credentials never leave the clinic.
- Which systems does Nidus connect?
- CRMs such as HubSpot, Salesforce and Pipedrive; EMRs such as VRepro and MedITEX; ERPs such as SAP and Sage; lab platforms such as Fairtility and AIVF; and patient apps such as Doctolib and EngagedMD.
- Who is Nidus built for?
- Private fertility clinics and clinic groups, typically running several disconnected systems across one or more sites, that need patient, treatment and appointment data to stay consistent everywhere.
- How is our data protected?
- Every clinic is a separate tenant with row-level security, so you only ever see your own data. Credentials are write-only and stored in a secrets vault. Nidus is built toward ISO 27001, ISO 27701 and SOC 2, with EU data residency for EU clinics.
- How long does it take to see value?
- We start with your highest-pain workflow, usually a conversion, retention or consent flow between your CRM, EMR and lab, and prove it on your own data in a focused first phase, then expand connector by connector.
See Nidus on your own systems.
A 30-minute walkthrough on your stack, VRepro included. We show what connects and what it unlocks.