The platform
Different workers.
One governed foundation.
Jackie, Sam, Joe and Robin perform different jobs, but they are built on the same Auxilis platform. Every new worker inherits the shared conversation engine, protocol controls, integrations, testing infrastructure, audit trail and safety machinery.
- Conversation engine
- Pathway controls
- Phone and text
- System integrations
- Testing and monitoring
- Audit trail
Phone and text
Support inbound, outbound and scheduled patient contact across the channels appropriate to the workflow.
Approved pathways
Control what the worker gathers, what it may do and when responsibility must return to a person.
Connected actions
Create structured records and complete approved work inside existing healthcare systems.
Human escalation
Route uncertain, concerning or out-of-scope interactions to the appropriate team with their context attached.
Governance and evidence
Maintain records of conversations, actions, workflow versions and escalation behaviour.
From pathway to deployed worker
Start with one job and one patient cohort.
-
Define
Agree the patient population, pathway, information requirements and intended outcomes.
-
Configure
Turn the approved pathway into a controlled conversation with defined actions and escalation boundaries.
-
Connect
Integrate the worker with the telephony, messaging and healthcare systems involved in the task.
-
Validate
Test the worker with realistic scenarios and clinical-safety oversight.
-
Deploy
Begin with a bounded cohort, measure performance and expand when the evidence supports it.
Integrations
Built to work inside existing systems
Auxilis workers complete approved actions and return structured records inside the telephony, messaging, clinical and operational systems teams already use — including EMIS Web, SystmOne, Accurx, Patchs and other form-based workflows.
EMIS Web 
SystmOne 
Accurx 
SystmConnect 
eConsult Common questions about the platform
What is an Auxilis worker?
An Auxilis worker carries out a defined piece of patient-contact work by phone and text — answering a routine request, preparing a review, running a scheduled check-in or confirming a patient’s status. It follows a pathway your service has approved, completes the actions that pathway allows, and returns a structured record to the responsible team.
Jackie, Sam, Joe and Robin do different jobs. Each is a worker on the same platform, not a separate product.
What do all the workers have in common?
Every worker inherits the same foundation: the shared conversation engine, the protocol controls that define what it may ask and do, the integrations into existing clinical systems, the testing infrastructure, the audit trail and the safety machinery.
A new worker is a new pathway on infrastructure you have already assessed, not a new system to assess from scratch.
How the human boundary and safety controls work Which clinical systems does the platform connect to?
The platform connects to EMIS Web, SystmOne, Accurx, SystmConnect and eConsult, so a completed action or structured record lands in the system a team already works in rather than in a separate interface.
Using something else does not rule it out. Auxilis builds the integration per system, wherever that system offers an API and meets the interoperability requirements the NHS expects.
How well do workers cope with accents and unclear speech?
The speech recognition behind every worker was selected specifically for British English, rather than a general-purpose system adapted for UK use afterwards. Performance across regional accents was an important part of that choice, and Jackie already answers patient calls at a practice in Liverpool, where she regularly handles a wide range of local accents successfully.
A worker also monitors how reliably it is understanding the conversation. If recognition is not working well enough — because of a speech difficulty, poor phone line, background noise or another issue — it routes the caller to a person automatically, without the patient needing to recognise the problem or ask to be transferred.
What happens when a worker cannot complete a request?
It hands over. Anything clinical, distressed or ambiguous — and anything outside the approved pathway — goes to a named person on your team with the information already gathered. The handover starts with context, not from the beginning.
The worker presents the picture. A healthcare professional decides what happens next.
What DCB0129, DCB0160 and DTAC ask of an AI system in the NHS How is a worker configured to our own pathway?
An approved pathway defines what the worker asks, what information it gathers, what actions it may complete and where the boundary sits. Auxilis configures the worker around that pathway, connects it to your systems and tests it before it handles live contact.
The pathway belongs to the service. The worker operates inside it.
Take routine patient contact off your team’s day.
See how an Auxilis worker could handle a defined patient workflow, complete approved actions and bring in your team only when they are needed.