Ella / synthetic workflow
A representative generic primary-care request, shown from first contact to review.
Follow one Ella consultation from reception to review.
Follow how information, safety checks, configured actions and review outputs stay connected. This is a product demonstration, not a clinical decision or a claim of live NHS integration.
Follow the sequence- 01
Reception
Start with identity and the reason for contact.
Ella confirms who is speaking, records consent and establishes what the person needs before a clinical pathway begins.
01 / 06Consultation state
Synthetic demonstration
Patient
“I have been getting a racing heartbeat on and off.”
Identity confirmedReason for contact capturedCorrect service pathway selectedWhy this stage matters
A single consultation state is opened and kept through the rest of the conversation.
- 02
Adaptive history
Ask the next useful question, not a fixed form question.
The conversation tracks what is known, what has been denied and which uncertainty is most useful to resolve next.
02 / 06Consultation state
Synthetic demonstration
Patient
“The episodes last about twenty minutes and happen every couple of days.”
Timeline updatedKnown answers not repeatedSyncope and chest pain prioritisedWhy this stage matters
The question plan changes as the patient answers instead of marching through every possible field.
- 03
Safety
Keep risk and uncertainty visible while the conversation develops.
Configured safety checks can be prioritised and unresolved findings stay visible for the next question and eventual reviewer.
03 / 06Consultation state
Synthetic demonstration
Patient
“No, I have not fainted and I do not have chest pain with it.”
Pertinent negatives recordedOutstanding safety checks retainedApproved safety-net wording availableWhy this stage matters
Safety information is part of the live clinical picture rather than a hidden end-of-call summary.
- 04
Configured actions
Move from conversation to the service workflow.
Where a pathway allows it, Ella can send a fixed link or message, issue a questionnaire, complete a supported form or prepare follow-up.
04 / 06Consultation state
Synthetic demonstration
Patient
“Yes, send the information to the email on my account.”
Recipient resolved by codeApproved template selectedDelivery receipt recordedWhy this stage matters
The model requests an allowed action; code validates the recipient, content and pathway before anything is sent.
- 05
Clinical review
Show the structured picture and the source together.
Authorised reviewers can inspect the working clinical picture, structured note and transcript without losing the patient's original account.
05 / 06Consultation state
Synthetic demonstration
Patient
“I mainly notice the racing sensation when I am sitting quietly.”
Summary updatedEvidence link retainedUncertainty kept explicitWhy this stage matters
The reviewer receives a starting point to verify, challenge and continue—not an automated clinical decision.
- 06
Output and follow-up
Prepare the record and the next operational step.
The same state can support a clinical note, transcript, supported PDF, coding workflow or an outbound follow-up configured by the service.
06 / 06Consultation state
Synthetic demonstration
Patient
“That covers everything I wanted to explain today.”
Conversation finalisedReview artifacts preparedFollow-up state retainedWhy this stage matters
One conversation can produce several bounded workflow outputs without fragmenting the patient record.
Human authority remains explicit
Prepared context is useful because it can be checked.
Ella can organise a conversation and request configured workflow actions. Authorised people and services remain responsible for clinical interpretation, diagnosis, prescribing, escalation and sign-off.