Workflows

Workflows that act on operations, not only on data

A signal appears in one system. Nidus applies a rule and acts in another, with an owner and a deadline.

Failed-cycle follow-upLive

If, System A

Cycle marked failed

EMR (VRepro) reports a negative beta

Nidus rule

Evaluate, prioritise, route

Needs follow-up within 48h

Assign owner

Start SLA

Task in CRM

Then: nursing contacts the patient within the deadline

How it works

An event, a rule and an action

Every workflow follows the same structure.

If, System A

Event, condition and context

The signal originates in one system when new data is recorded.

Nidus rule

Evaluate, prioritise and route

The rule determines the relevance of the event and who it corresponds to.

Then, System B

Assign, alert or update

It assigns an owner, creates an alert, starts a deadline or updates a record in one or several systems.

Example. A cycle is recorded as failed in the clinical record. Nidus creates a follow-up task in the CRM with an owner and a deadline.

Catalogue

Workflows organised in three families

Each clinic activates the workflows it needs. The group keeps the same criteria across all sites.

Quality, conversion and retention

Consent, follow-ups and patient journey.

Operational efficiency

Billing, cryopreservation, reporting and duplicate removal.

Full ecosystem

Procurement, laboratory witnessing and clinical artificial intelligence.

Operational management

Owners, queues and deadlines

A workflow does more than move data. It creates tasks with an owner and a deadline, and gathers pending issues in a single queue.

→An owner assigned to every follow-up
→A resolution deadline tracked until closure
→A single queue with all pending issues

Operations queue

Beta negative follow-up
Nursing48h SLA
Missing consent
Admin4h SLA
Deposit unpaid
Finance2h SLA

Examples

Common workflows

International lead routing

When a lead arrives from another country, it is routed to the right site and coordinator, in the patient's language.

Appointments and budgets to the CRM

Appointments, budgets and treatments from the clinical record are shown in the CRM.

One record across sites

A change recorded at one clinic updates the group's single record, so every site works from the same data.

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.

Request a demo