Care that never runs out of time.
Florence calls patients, brings staff into the conversation when the workflow requires it, and records the outcome. NightingaleMD builds each workflow around your protocols, systems, and human handoffs — while clinical judgment stays with your team.
Start with a template. Build the workflow around your operation.
NightingaleMD provides reusable templates for care pathways, multi-step workflows, and longitudinal programs. Our healthcare engineers adapt them to your protocols, systems, tools, and handoff rules. The result is your version — versioned, testable, and auditable.
Connect the systems this workflow needs
We build connections for commercial, custom, and homegrown systems through the same integration framework. Configured connector operations can write approved outcomes; connector-specific rules determine how delivery is verified.
What Florence may do
Book, text, conference your clinic in, look up the roster, file the note — each capability granted per task, per workflow step. What isn’t granted structurally cannot happen.
Your rules for the hard moments
Who gets flagged, when Florence transfers, which situations reach a nurse now versus tomorrow’s worklist — encoded to your protocols, from after-hours coverage to named emergency routes.
Safety controls set before launch
Protected workflows use configured identity checks, consent and quiet-hour controls, and explicit human handoffs. Florence is not authorized to diagnose, prescribe, or direct treatment.
See the workflow engine, release checks, and available audit evidence on the platform page.
Explore the platform →Three layers, built for the outcome you define.
We start with reusable templates at each layer, then build your version around the questions, actions, systems, and human handoffs your team defines.
Pathways
Within a conversation, a pathway defines what Florence asks, what she flags, and where each answer routes.
Workflows
Across an episode, a workflow coordinates invitations, calls, bookings, reminders, documentation, and human follow-up.
Programs
Across an ongoing relationship, a program sets the cadence, carries approved context between sessions, and reports the outcomes your team chooses to track.
Each layer hands a defined result to the next: a pathway hands a disposition to the workflow; a workflow hands an outcome to the program. That separation keeps each custom version inspectable.
Follow the conversation and the structured record together.
The demonstration pairs Florence’s conversation with the workflow state and tool activity behind it, so your team can inspect the handoff, the configured actions, and the resulting record together.
No form, no gate. When you’re ready to see it on your workflow, request a workflow review with the team that builds the platform.
One conversation closes one loop.
Florence identifies herself as an AI on behalf of your care team. Configured protected workflows run server-side patient matching, then work the task toward a recorded outcome.
Reach
Calls and texts inside quiet hours. A familiar number helps recognition; identity never relies on caller ID.
Verify
Configured protected workflows use server-side patient matching against roster or EHR fields. Unresolved matches route to staff.
Converse
A real conversation in the patient’s language — running the pathway your protocols define.
Book
Florence conferences your clinic in and books the visit with the patient still on the line.
Document
The workflow records the outcome. Configured chart-delivery steps write structured documentation and verify that it landed.
When a configured clinical flag is triggered, the pathway transfers the conversation or routes it to your team according to your rules. Staff receive the conversation, the reason for the flag, and the configured handoff destination.
Run one approved workflow across a patient cohort.
Load a patient list and launch the workflow you approved. Each patient follows its outreach, booking, documentation, and handoff rules, with consent, opt-outs, and quiet hours enforced in code.
Your team sees completed steps, open tasks, and conversations that need a person. An escalation here is the system working, not failing.
Medicine has always rationed its minutes. Florence makes time abundant.
Care teams lose time to dialing, re-dialing, documenting, and chasing follow-up. Florence takes on that repeatable work, leaving licensed staff focused on questions that need clinical judgment.
With more time for conversation, she can ask about the practical details around a diagnosis: whether there are stairs between the bed and the bathroom, whether a prescription was picked up, and who is available to help. The relevant context returns to the care team.
“Scarcity of time built the healthcare we have. Abundance of time is how we build the one we want.”
Show your compliance team the evidence behind each control.
Florence talks. Only the engine acts.
Care state advances only through typed, logged steps. Anything ambiguous is parked for a person — never quietly marked done.
Safety scenarios run on the production voice pipeline
Published scenarios drive full conversations with synthetic participants through the deployed production voice pipeline. An errored run never counts as a pass.
Connector-specific confirmation
Configured connector operations can write approved outcomes to the system of record. Connector-specific confirmation rules determine how delivery is verified.
Tenant isolation tested at the database layer
Database row-level security and adversarial tests enforce tenant separation. Calls retain the prompt and workflow versions plus logged events available for review; evidence coverage is shown during diligence.
“Florence is configured to ask, record, and route. Clinical judgment stays with licensed staff.”
23 supported languages. One accountable workflow.
Florence supports 23 voice languages. We validate each deployed workflow in the languages it uses; interpreter mode is available on configured three-way calls.
Built for the teams doing the work.
Value-based care providers
ACOs, FQHCs, and primary care groups: close the loops your quality and revenue already depend on.
See how →Health systems
Post-discharge follow-up, referrals, and scheduling that stop leaking between departments.
Health plans
Member outreach with the audit trail, consent handling, and escalation discipline your oversight requires.
Digital health companies
Intake and engagement at scale, integrated with your own systems — even a custom EHR.
See how Florence would run it.
Bring the protocol, patient journey, and systems your team uses today. We’ll map the pathway, workflow, tools, and human handoffs together.