Build the care workflow you need — and keep each automated action on the record.
NightingaleMD starts from reusable templates for pathways, workflows, and programs, then adapts them to your protocols, systems, tools, and handoff rules. Each deployed version records what Florence was allowed to do, what she did, and how the journey ended.
Templates where they help. Custom where your operation demands it.
Connections, tools, escalation rules, and clinical safeguards are assembled into your version. You do not have to reshape care delivery around a generic settings page.
Connections — your systems, first-class
A dedicated integration framework for EHRs and everything around them — including custom and homegrown systems. Credentials are sealed, operations are allow-listed, and connector-specific rules determine how each approved delivery is verified.
Tools — only what this workflow needs
Everything Florence can do — book, text, conference, look up, file — is a typed tool granted per workflow step. Phone numbers are bound before the call starts; a tool that isn’t granted structurally cannot be used. Custom tools for your operation are built on the same contract.
Escalation rules — your judgment, encoded
Which phrases warm-transfer to a nurse now, what lands on tomorrow’s worklist, who is on the other end of the line after hours — your protocols become explicit routes with explicit destinations. Designed with your clinical leads, versioned like everything else.
The configured clinical floor
Platform safeguards apply first. Account, workflow, campaign, and patient settings may only make them stricter. Protected workflows use configured identity checks, consent and quiet-hour controls, and human handoffs. Florence is not authorized to diagnose, prescribe, or direct treatment.
Custom-built at three layers.
A pathway controls one conversation. A workflow coordinates one episode. A program carries approved context across an ongoing relationship. We start from templates at each layer, then build around the outcomes and handoffs your team defines.
Worked example: a pathway asks and routes the questions in one call; a workflow follows up and documents the episode; a program sets the cadence and approved context for the ongoing relationship.
Florence can talk. Only the engine can act.
Configured workflows run on a deterministic engine. A patient’s journey advances through typed, logged steps rather than spoken claims alone. Ambiguous workflow outcomes route to a human.
The gold station is deliberate: an escalation to a human is the engine behaving correctly — never a failure state.
A voice build passes its tests and its startup check before it takes calls.
Every required test suite must pass before a build deploys. The new voice build passes its startup check before it takes calls, and the live voice endpoint is checked right after. Published safety scenarios use synthetic participants over the deployed production voice pipeline.
errored eval run: never a pass
Safety controls built into the platform.
SOC 2 Type 2 observation period began September 15, 2026 · independent report targeted December 2026 · status as of October 2, 2026
Confined by construction
Florence’s tools are granted per task, and phone numbers are bound before the call ever starts — she structurally cannot dial a number she wasn’t given, no matter what anyone says to her. A capability that isn’t wired can’t be misused.
Server-side matching for protected workflows
Caller ID is never treated as proof. Configured protected workflows match patients against fields in your roster, EHR, or chosen source of truth — such as name, date of birth, or medical-record number. Unresolved matches route to staff.
Consent and quiet hours, in code
Quiet hours follow the patient’s own timezone. A STOP reply records an opt-out and blocks future automated outreach in that care organization. Consent is attested before a campaign can launch.
Reconstructable, end to end
Calls retain the prompt and workflow versions plus logged events available for review. We show the current evidence coverage during security diligence.
23 supported languages, governed by the same 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.
What we can build with you.
We start with reusable templates, then adapt the questions, cadence, systems, tools, and human handoffs to your operation.
Telephone-triage pathways
Adapt pathway templates to your questions, escalation destinations, and coverage model.
Longitudinal care programs
Define the cadence, approved context, consent rules, and reporting for an ongoing care relationship.
Family and caregiver workflows
Set consent-aware participation rules for when a patient wants a family member on the line.
Bring the hardest workflow in your operation.
Clinical, security, and engineering reviewers welcome. We’ll show how the templates adapt to your rules, tools, and systems.