The platform
A fertility data platform, in three layers.
A semantic core that ingests every system, a cockpit for full visibility, and a catalogue of workflows that act on the data. Connectors bring systems in; workflows act across them.
nidus core
Connectors + fertility data model.
nidus cockpit
Visibility, analytics and control.
nidus workflows
Cross-system automation catalogue.
nidus core
One fertility data model, reused everywhere.
Nidus core translates fragmented clinic data into mapped concepts that can be reused across systems and workflows, with a governance layer for data quality, validation, lineage and multi-tenant security.
Core fertility entities
Person
Individual info: demographics, contacts, consent
Partner
Relationship & role in the fertility journey
Patient Unit (Couple)
The fertility unit; clinical & operational centre
Cycle
IVF / ICSI / IUI / FET / donor cycles and attempts
Episode
A clinical episode within a cycle
Embryo
Embryo lifecycle: creation → transfer / cryo / disposition
Supporting entities
Cross-cutting & governance
Connectors
Bridges that bring each system into the model.
A connector determines whether Nidus core can ingest a system's data. We prioritise them by repeatability, economic pain and proximity to conversion and retention workflows.
Clinical (EMR)
CRM
Cryo / inventory
Billing
Lab (LIS)
CRM
Billing
Patient portal
On-premise and IP-whitelisted systems (such as VRepro) are reached through a secure, outbound-only egress agent, with no inbound network changes at the clinic.
nidus cockpit
Complete visibility across clinic data and workflows.
One interface for the clinic or the whole group: connection status, the patient journey, analytics and workflow control.
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
- Status overview
- A quick view of connection status: systems connected, live workflows and health.
- Patient journey
- The full journey with the ability to deep-dive any phase to analyse stats or quality.
- Analytics
- Configure specific analytics using natural-language prompts. Ask your data a question.
- Workflow control
- Activate, freeze or modify workflows, and pick new ones from the Nidus catalogue.
- Workflow creator
- Build your own workflows in a no-code environment.
nidus workflows
Automations that act on the data.
A workflow watches for a signal in one system, applies a Nidus rule, and takes action in another. Workflows are organised into families that make up the Nidus workflow catalogue.
If, System A
Event · Condition · Context
Signals originate in one system as new data appears.
Nidus rule
Evaluate · Prioritise · Route
The rule decides what matters and where it goes.
Then, System B
Assign · Alert · Queue · SLA · Update
The event impacts one or many other systems.
Quality, conversion and retention
Consent, follow-ups and patient-journey workflows.
Operational efficiency
Billing, cryo and BI workflows that remove duplicate work.
Full ecosystem
Procurement, e-witnessing and clinical-AI integrations.
See Nidus on your own systems.
A 30-minute walkthrough on your stack, VRepro included. We show what connects and what it unlocks.