Healthcare AI agents can act in different ways, but there is no meaningful company-wide yes-or-no answer to whether a product is autonomous. As of 9 October 2026, a useful comparison must identify the exact feature, intended user, location, availability stage and approval boundary. A London documentation preview is not the same proposition as a Utah prescribing pilot.
This tracker is published by iatroX and includes iatroX as a clinical-reference and education category, not as an autonomous-care provider. The entries describe documented scope and availability, not a hands-on test of every account, integration or regional deployment.
Read the action before the brand
Five distinct activities help make the comparison precise. A system can answer a question, prepare a draft, propose a decision, execute an already authorised task or make a bounded decision under a specific service arrangement. These categories are an editorial framework, not formal regulatory classes.
The distinction matters at the point of consequence. Producing the words of a referral does not establish that it was approved, delivered or accepted. Similarly, collecting a history does not establish that a clinician has assessed it. Product descriptions should identify which transition the software actually supports.
Authority is a separate field from capability. Software might technically be able to send a message while lacking permission to do so for a particular patient. A prescribing pilot can permit a narrowly defined action without authorising broader primary-care decisions. Neither model fluency nor tool access settles that boundary.
The availability-and-capability snapshot
All entries below are dated 9 October 2026. TORTUS Health's entry uses the service materials recorded in that date's supplied research; the other linked entries were checked against their public documentation. Unknown local configurations remain unknown.
| Product and exact feature | Intended user and location | Availability stage | Action and approval boundary |
|---|---|---|---|
| TORTUS Health virtual care | Eligible patients, California-first | Staged access described | AI gathers information and proposes care; clinician approval required |
| TORTUS AI documentation | Clinical organisations, UK NHS-facing | Deployed product, local access and integration vary | Notes, letters and suggested codes; clinician-approved filing |
| Heidi II agents and Routines | Clinicians and teams in supported markets | Rollout began 29 September 2026; UK and EU excluded | Workflow execution with configurable approval controls; not unrestricted prescribing |
| Amazon Connect Health ambient documentation | Organisational deployments, Europe/London | Preview from 14 September 2026 | Draft clinical documentation for provider review |
| Amazon Connect Health appointment management | Organisational deployments in supported US regions | Listed US feature availability | Scheduling actions through configured patient-engagement workflows |
| Nolla Utah acne pilot | Eligible Utah patients | Bounded pilot | Initial treatment within the defined pathway, with staged oversight |
| Doctronic Utah renewal pilot | Eligible Utah patients with existing prescriptions | Bounded pilot | Restricted renewal; not new treatment or changes under the renewal pathway |
| iatroX reference and learning | Clinicians and learners | Available under September 2026 specification | Referenced questions and professional practice, not clinical workflow execution |
The supporting sources are TORTUS Health, TORTUS AI, Heidi's launch release, AWS regional documentation, Utah's pilot descriptions and iatroX's methodology. Read the feature-level qualification with each row rather than treating availability as a universal brand attribute.
Why preview, pilot and rollout mean different things
A preview describes a release stage, not a clinical permission. A regulatory pilot describes an arrangement for testing within specified conditions, not a promise that every eligible person can access it immediately. A staged rollout can release capabilities incrementally by market, customer or configuration.
The Utah sandbox explanation, checked on 9 October 2026, explicitly distinguishes participation from state endorsement or product approval. A signed agreement should also be distinguished from the beginning of its demonstration period. Permission, launch and completed evaluation are separate milestones.
For an organisation making a buying decision, an announcement is therefore insufficient. It needs confirmation that the particular feature is accessible for its location and deployment. The status should be recorded in the procurement file, not reconstructed later from a global marketing page.
Human approval needs a more specific description
A tick beside human oversight conceals important differences. Approval before action, review afterwards, sampled audit and access to a clinician on request are not the same control. Even prospective approval can vary according to what the reviewer sees and what they can change.
For each proposed workflow, ask who provides the clinical decision, who permits the technical action and who confirms completion. Sometimes those roles belong to different people or systems. The record should make their relationship visible rather than rely on a single approved label.
The FDA's January 2026 guidance also distinguishes software functions by their role. It is a useful reminder not to treat a multifunction platform as having one undifferentiated clinical status. This tracker describes product boundaries, not a legal determination for a particular deployment.
A practical example of a misleading capability comparison
Suppose a fictional hospital compares two suppliers using a column labelled follow-up. One can draft a patient message. The other can send an authorised message and record a delivery response. Both receive a tick, although the organisation still needs different staff work after each output.
Now suppose the second product's sending feature is available only in a different market. The original comparison has combined a functional mismatch with a regional mismatch. Neither problem is resolved by the supplier having an impressive demonstration elsewhere.
A better record would identify the requested action, the supported destination, the approval required, the evidence of completion and the fallback when the action fails. This is a proposed procurement method. It does not imply that a named supplier has misrepresented its product.
Dated change log
On 14 September 2026, AWS's documentation dates the start of ambient-documentation preview in Europe/London. That entry does not extend the London preview to all Connect Health features. The regional table should remain the source for subsequent feature-specific changes.
On 28 September 2026, Heidi announced Heidi II, with rollout beginning on 29 September. Its release specified that the new capabilities would not be available in the UK or EU. This qualification should not be extended to every existing Heidi product.
The 9 October 2026 review adds TORTUS Health's California-first, clinician-reviewed care proposition and separates it from TORTUS AI's NHS documentation role. It also records the distinction between Nolla's bounded initiation pathway and Doctronic's renewal pathway. No later availability change is implied by this snapshot.
How to use the tracker
For a UK clinical buyer, start with the regional feature and local implementation rather than an international launch headline. For a patient-facing service assessment, start with eligibility, clinical authority and the route to a person. For a researcher, specify the exact system configuration being evaluated.
For a clinician seeking knowledge or learning support, iatroX belongs in a different comparison. Its September 2026 specification covers source-linked reference and structured professional practice, not autonomous treatment or record execution. The useful choice is the tool that supports the intended task under the right conditions, not the company with the broadest use of the word agent.
Frequently asked questions
Are all Amazon Connect Health agents available in London?
AWS's documentation, checked on 9 October 2026, lists ambient documentation in preview for Europe/London. It does not list every US feature as available in that region.
Is Heidi II available in the UK?
The September 2026 launch release excludes the new Heidi II capabilities from the UK and EU. That statement should not be applied indiscriminately to existing Heidi products.
Does a healthcare AI pilot mean the product is approved for general use?
No: a pilot has its own scope and conditions. Utah explicitly states that sandbox participation is not state endorsement or product approval.