Submit patient requests into the online-consultation and triage systems UK GP practices actually run, as structured, first-person triage entries. This is how a phone call, voice-agent conversation, or intake record becomes a request sitting in the practice’s own triage queue, running in production at UK practices today.
Overview
UK general practice runs on online-consultation forms. Each practice uses one of a handful of triage systems, and each system has its own login flow, its own taxonomy of request tiles, its own body-map and questionnaire widgets, and its own submit ritual. There is no API; the form is the interface. This workflow takes a structured patient request from your upstream intake, a phone call handled by a voice agent, a web form, a call-centre note, and submits it into the practice’s specific triage system exactly as the practice has configured it.
Every practice is set up as its own agent: same skeleton (sign in where required, select the right request tile, complete patient details, submit, confirm), different configuration. Time-of-day routing changes, per-practice request categories, and follow-up-versus-new-request paths are handled as variants of the same build, because that’s how real practices operate.
Step by step
Every one of these agents follows the same rule: the patient’s own description, in the first person, goes into the form verbatim. A triage clinician deciding urgency from “I’ve had a crushing pain in my chest since breakfast” is working with clinical signal; one reading “patient reports discomfort” is working with a transcription loss. Automating the submission is only acceptable if the automation adds nothing and removes nothing.
At scale
This runs in production across UK practices today, downstream of voice-agent phone intake: the call ends and the triage entry exists, with no receptionist re-typing in between. Each additional practice is a configuration of the same skeleton, which is how deployments scale to dozens of practice-specific agents, including the odd practice whose routing changes before 9am. It composes upstream with any intake source that produces structured patient requests, and sits alongside inbound referral capture in the referral-intake library.
Human in the loop
All patient data is processed on UK-GDPR-compliant, SOC 2 Type II infrastructure, with a per-execution audit trail showing every field submitted. Details on the security page.
Any evidence of an emergency.
The screening step never downplays a red flag to get the form through; the case goes to a person immediately.
A tile or question the configuration doesn’t cover.
Practices reorganize their triage taxonomies; an unrecognized layout stops the run rather than guessing a category.
A rejected or partially accepted submission.
If the system doesn’t clearly confirm, the outcome is reported as failed with the exact state observed, never assumed delivered.
Questions
Every request a receptionist re-types from a call into a triage form is a transcription step that adds delay and subtracts fidelity. The referral-intake library covers the rest of the inbound path.
Disclaimer
Third-party names, including government agencies and registries, are used only to identify systems commonly involved in healthcare operations workflows. Asteroid is not affiliated with, endorsed by, sponsored by, or certified by those third parties unless expressly stated. Workflow availability depends on customer authorization, account permissions, configuration, and applicable system terms.