Existing documentation products and newly announced AI capabilities should not be treated as the same offer. As of 22 September 2026, Heidi's announcement excludes its forthcoming capabilities from the UK and EU, not its entire existing service. Tandem's wider clinic operating system is an expansion roadmap, while access to particular functions depends on market and delivery channel.
This article is published by iatroX and includes iatroX among the tools discussed for clinical reference. It is a public-documentation comparison, not a hands-on certification of local availability.
Read the regional qualification narrowly
The important wording in Heidi's September 2026 announcement concerns the forthcoming capabilities described in that announcement. It should not be rewritten as "Heidi is unavailable in Britain", "Heidi is leaving Europe" or "all Heidi AI agents are prohibited". None of those broader conclusions follows from the qualification. Heidi's accompanying release is the source for the limited statement.
The distinction matters for existing customers. A practice may be able to continue an established documentation workflow while a newly promoted capability is not offered to it. A global product page may also describe a broader experience than the practice's current agreement includes. The purchasing question is therefore the exact function available through the exact account, not whether the company operates in the country at all.
Do not speculate about the reason for the regional restriction. Regulatory strategy, contracting and release sequencing are different possibilities, but the announcement does not establish which explanation applies. A request for clarification is more useful than an unsupported account of the company's motives.
Availability matrix: public documentation checked on 22 September 2026
This matrix records what the reviewed sources support. "Not confirmed" means the public material did not establish the precise entitlement; it is not a finding that the function does not exist.
| Product and route | Documentation | Evidence or reference | Integration scope | Proposed wider actions |
|---|---|---|---|---|
| Heidi through a UK organisation or individual account | Existing product publicly described; exact plan and organisation approval must be checked | Evidence publicly described; exact local in-session and out-of-session entitlements not confirmed here | Requires confirmation for the named clinical system and purchased configuration | Forthcoming capabilities in the September announcement are excluded from the UK |
| Heidi through an EU deployment | Existing service should not be conflated with the new restriction; country and account scope need confirmation | Country-specific sources and entitlements not confirmed here | Country, system and contract-specific scope not confirmed | Forthcoming capabilities in the September announcement are excluded from the EU |
| Tandem through a direct European deployment | AI scribe and related assistant functions publicly described | Clinical Decision Support publicly described; market-specific entitlement requires confirmation | Public integration catalogue, not proof that every connection supports every function | Broader clinic operating system is an announced expansion direction |
| Accurx Scribe through a UK organisation | Partner-delivered product built on Tandem technology | Inclusion of all Tandem reference functions not confirmed | Accurx describes clinical-record write-back; local deployment scope requires confirmation | Do not assume Tandem's whole roadmap is included |
The source set comprises Heidi's announcement, Heidi Evidence, Tandem's funding roadmap, Tandem's integration catalogue, Tandem Clinical Decision Support and Accurx's partnership announcement. The last was published on 27 May 2025; it establishes the partnership and described functions, not a current entitlement for every organisation.
Accurx is a delivery channel, not an interchangeable label
Accurx's 27 May 2025 announcement describes Scribe as built on Tandem's technology and discusses documentation, referrals, Advice and Guidance requests and follow-up communications. That is already broader than passive transcription. It does not justify giving every current Tandem function an automatic tick under Accurx Scribe. Accurx's description is the relevant starting point.
When a clinician says "we have Tandem", the next question should be whether access is direct, partner-delivered or configured through an employer. This changes the support route, feature set and implementation responsibilities. The brand name alone cannot answer a question about a button in a local workflow.
The same discipline applies to Heidi. The presence of a function in global marketing does not establish that it is active in every UK account, included at every price point or connected to a particular electronic record.
A fictional cross-border procurement problem
Consider a healthcare group with a UK outpatient service and an EU clinic. The group likes a global demonstration that combines a note, a source-linked answer and a prepared patient message. It wants to purchase one consistent workflow.
The buyer separates the demonstration into those three activities. For each site, it asks the supplier to state whether the activity is available now, included in the proposed contract and connected to the local record. Where a function is not confirmed, the group leaves the cell open rather than substituting a global screenshot.
The resulting procurement might reasonably be different at the two sites. One could adopt documentation while retaining its existing messaging process. The other might defer a wider rollout. Consistency is valuable, but forcing an unverified equivalence between deployments can hide the very implementation work the organisation needs to understand.
What a useful request for information asks
Request the product name, release or version, country of deployment and purchasing route in the same response. Ask which functions are included, which need configuration and which are roadmap items. A broad statement that the supplier "integrates with" a clinical system is not sufficient.
Ask the supplier to demonstrate what is read, what is written, who reviews it and how successful transfer is confirmed. Include permissions, training, local support, downtime handling and the process for reporting an incorrect output. An organisation should also know which team will own exceptions when a generated item cannot be completed.
A useful reply gives named responsibilities and a demonstrable workflow. An unhelpful reply supplies only a feature list and a global customer logo. Neither the size of a financing round nor the existence of an integration catalogue removes the need for those operational answers.
Source relevance is another kind of locality
Per iatroX product information, September 2026, Ask-iatroX provides free reference grounded in NICE, CKS, SIGN and SmPC information from emc, with linked sources and a published retrieval and checking methodology. That UK-facing source design is a different consideration from whether a documentation product can be purchased locally. It does not make every answer correct or replace local policy.
A source may be authoritative yet not answer a particular service's operational question. A clinician should distinguish national guidance, product information and the organisation's own pathway. Assessing that distinction belongs in clinical-reference evaluation, not in a table of recording hardware or scribe integration availability.
Verdict by deployment scenario
For an existing UK Heidi customer, check the current contracted service separately from the newly restricted capabilities. For an Accurx organisation, evaluate the actual Accurx Scribe workflow rather than importing the entire Tandem catalogue. For a cross-border buyer, require a separate country-level specification. For a clinician seeking UK reference and learning, consider iatroX for that task without treating it as documentation infrastructure.
Frequently asked questions
Are Heidi's existing products unavailable in the UK and EU?
The September 2026 qualification concerns forthcoming capabilities in the announcement, not all existing products. Exact functions still require a market-specific account or contract check.
Does an integration listing prove full write-back?
No: a listing alone does not establish which data can be read or written, under which permissions or with what review. Ask for the specific workflow in the intended configuration.
What does not confirmed mean in this comparison?
It means the public sources checked on 22 September 2026 did not establish that precise local entitlement. It should not be interpreted as proof of absence.