LifeLines / ModulesAutomations

The next step, taken for you.

Say it in a sentence or draw the steps. LifeLines takes them on every case, by itself.

Book a demo Build a combination

| Automations6Alex

AutomationsFirst reading reminderVersion 2 is live

TriggerConditionBranchWaitRun togetherActionStop

TriggerStartDevice delivered

Delivered

ThenWait

WaitWait

2 days

ThenNo reading yet?

ConditionNo reading yet?

1 rule, all must match

YesSend a text

NoStop

ActionSend a text

Reminder: please take your first reading today.

ThenDrag to connect

StopStop

Ends the automation

Drag a step to move it. Drag an exit dot onto another step to connect them.

What it replaces

The follow-ups nobody has to chase.

~~Text each patient on delivery~~Delivered sends the text
~~Move each case by hand~~A step moves the case
~~Remind the care team yourself~~The people on the case are told
~~Copy details into other software~~A request passes them on

What it can do

Anything that happens, handled.

Pulse

Say it in a sentence. Pulse draws it.

Describe what should happen. Pulse draws the steps for you to check.

No blank canvas to start from

New automation

Build it yourselfName it, then add the steps on the canvas, or paste an automation you copied.

Describe it to PulseSay what should happen, and Pulse draws the steps for you to check.

PULSEWhat should happen?

Two days after the device is delivered, text the patient a reminder to take their first reading.

When a case is approved for RPM, wait one day, then text the patient a welcome message.When a scheduled call is missed, notify the people on the case.

It opens on the canvas as a draft, turned off. Nothing runs until you publish it.

Cancel

Triggers

Starts on anything in LifeLines.

A new case, a reading, a call, a text, a delivery, a claim or a date.

Every module can start one

What starts this automation?

Search every event, or pick a section to browse it.

Search events…

Common7Case & Patient43Encounters20Calls18General Notes3Orders & Shipments26Status Changes4Dates3Advanced19

CommonNew Case CreatedA case is started by hand in the app.RPM consent form signedThe patient signs the RPM consent form.DeliveredA device or a letter is delivered. Narrow it by what was delivered.Case Status EnteredA case enters a Case Status. Narrow it by the status.Missed Scheduled callA scheduled call with the patient is missed.Call EndedA call ends.Patient MessageA text is sent to or received from the patient. Narrow it by who sent it.

Steps

Does the work on the record.

Text the patient, update the case, add a note, tell the team or call another system.

No step done by hand

ActionSend a text

Hi John, your device has arrived. Please take your first reading today.

ActionUpdate the case

Show a Case Notice: No reading since delivery

ActionAdd a note

Reminder texted two days after delivery.

ActionNotify staff on this case

The people on this case: No reading yet for John Doe

ActionSend an HTTP request

POST lab.example.com

From any module

Set it up where you work.

A setting in another module opens Automations with its event already picked.

One click from the setting

Ranges by device typeMissed readingsReview and escalationAssignmentWorking daysRPM lineExtra alertsAutomatic claims

Extra alerts

Every readingStarts on "Reading Received".Set up an automation

Critical readingStarts on "Critical Reading Received".Set up an automation

Device issueStarts on "Device Issue Reported".Set up an automation

Follow-up missedStarts on "Follow-up Missed".Set up an automation

Review closedStarts on "Review Closed".Set up an automation

Safe by default

Nothing runs by surprise.

Try it

See the path before it runs.

Try it on a real case. Every step it would take is shown, and nothing is sent.

Checked before anyone gets a text

Try itWhat this automation would do, as the canvas stands now.

On a caseWithout a case

Case IDC-RPM-519274083

Nothing is sent and nothing is written to the case.

Try it

Case C-RPM-519274083 would go this way

1Device deliveredStarts here. The event is taken as having happened.
2WaitWould wait 2 days.
3No reading yet?Yes, so it goes the Yes way.
4Send a textWould send the text.

"Send a text" has no next step, so the automation ends there.

Publish

Off until you turn it on.

Publishing freezes a version. Runs already going keep the version they started on.

Yours3SystemFailuresHistory

New automation

AutomationStatusTurned on

First reading reminderLive

Welcome text after approvalDraft-

Follow-up after a missed callOff

Welcome text after approvalDraft, not published

Publishing freezes this draft as version 1. It stays turned off until you switch on Turned on.

Publish

Failures

A failed step is never quiet.

It is tried again, then listed under Failures with what went wrong.

YoursSystemFailures1History

First reading reminderStep: Send a textOpenLast seen 2h ago

The step "Send a text" could not run. It failed once and this automation has stopped trying.

Seen once, first on Oct 27 2026 09:14

Resolve or dismissRequeue

The details

And the details.

Describe it to PulseType what should happen; Pulse draws the steps.
Try itRuns on a case without sending or writing anything.
VersionsPublishing freezes a version; running cases keep theirs.
FailuresA failed step is retried, then listed with the reason.
HTTP requestA step can pass case details to another system.

Connects with

What it works with.

A connection works while both are on. Switch the other off and Automations keeps working.

EHREvents on a case start it.CommunicationsThe Send a text step.Orders & ShipmentsShipping triggers.BillingClaim triggers.Remote MonitoringReading and review triggers.DeveloperWebhooks.

Your softwareThe Send an HTTP request step.

AutomationsNext steps, taken for you.

Add any of them, whenever

EHR Communications Remote Monitoring Billing Orders & Shipments Inventory Analytics CRM Queues Developer

Book a demo

Tell us your combination.

We will show you how it fits the way you work.

Or write to sales@lifelines.health