An NHS clinician using Accurx Scribe may reasonably wonder whether Tandem's Sovereign Health announcement changes the service in front of them. The answer cannot be inferred from the partnership alone.
Accurx Scribe uses Tandem technology, but a new option advertised by an underlying supplier is not evidence that every partner-delivered deployment has migrated to it. Availability, contracting, configuration and local approval remain separate questions.
This update explains how to establish what applies to an actual NHS implementation. It preserves the distinction between Tandem's product development and Accurx's route into clinical work, rather than treating the two companies as unrelated competitors or interchangeable services.
The partnership predates the new offering
Accurx's announcement of 27 May 2025 describes Accurx Scribe as built on Tandem's AI scribe. It discusses documentation, related drafts and record-system write-back through the Accurx environment.
The announcement's reference to more than 200,000 staff concerns an access and rollout proposition, not a verified count of people actively using the scribe. The distinction remains important when reading later product announcements.
Tandem's September 2026 financing added resources and stated expansion ambitions. It did not create the original partnership or establish which subsequent Tandem functions would appear in every Accurx contract.
A product relationship can provide distribution without making all deployments identical.
Four stages that should not be collapsed
A feature can be announced before it is available to a particular customer. It can be available before the customer purchases it. It can be purchased before its local assessment is complete. It can be approved before every relevant user is actually using it.
For a clinician, the useful endpoint is the configuration operating in their service today. For the implementation lead, the useful record also includes planned changes and the conditions for introducing them.
| Stage | Evidence that would establish it | What it does not establish |
|---|---|---|
| Supplier announcement | A dated description of an offering | Access through a particular partner |
| Availability to the customer | A scoped supplier confirmation or quotation | Local permission to use it |
| Organisational acceptance | A documented assessment and decision | Completion of every migration step |
| Live operation | Confirmed configuration and relevant use | Identical behaviour in another organisation |
This is an original implementation framework. It is not a description of Accurx's internal release process.
Identify the deployment before discussing sovereignty
Start with the name of the service and the route through which it is supplied. Establish the contracting entity, the organisation administering access and the current processing arrangement.
A desktop application, browser access and a mobile route may involve different operational details. Do not assume that a familiar interface answers where transcription or model processing occurs.
The local implementation lead should be able to connect the product in use to the relevant supplier information and approval record. Individual clinicians should not have to reconstruct that relationship from several companies' marketing pages.
The European-cloud and NHS-data guide explains why legal entities and processing stages need to be considered together.
Ask whether Sovereign Health applies to this route
The Sovereign Health explainer describes the enterprise option published by Tandem. What remains to be established for an Accurx customer is whether that option is available through its own arrangement and, if so, what changes.
Request a specific answer about the existing deployment, not simply confirmation that the companies work together. The answer may concern a separate contract, a future option or a configuration already assessed locally. Public material alone does not settle which applies.
Avoid both unsupported assumptions: that everyone has already migrated and that no partner customer could access the option. The correct position is a deployment-specific question for the organisations supplying the service.
Keep enabled functions separate from the wider platform
An underlying supplier can advertise documentation, coding and clinical decision support without every partner implementation exposing all three in the same way.
List the functions staff actually use. For each, identify what information enters, what output appears, who reviews it and what happens after approval.
A clinical-information feature deserves examination on its own terms. A benchmark assessing generated notes should not be used as the sole evidence for the clinical advice a user receives elsewhere in the platform.
Similarly, a demonstration of record write-back should establish the destination, version and confirmation of transfer. It is not evidence that every referral, patient message or task has reached a clinically appropriate endpoint.
The task-specific validation article provides a practical matrix for keeping those questions distinct.
A ready-to-use message for the implementation lead
The following original message can help a clinical team request a concrete answer without assuming a migration has occurred:
We are reviewing the implications of Tandem's Sovereign Health announcement for our Accurx Scribe deployment. Please confirm whether the offering applies to our current contract or is available as a separate option.
Please provide the current and proposed processing arrangements for the functions we use, including the relevant suppliers and model operation. We also need to know whether any change affects note behaviour, coding, record transfer, retention, support access or patient-facing information.
Please identify the supporting evaluation and assurance documents for the proposed configuration, the local decisions required before use, and how users would be informed of the change. Please also confirm the practical migration, continuity and exit arrangements, including any additional costs.
The message requests information; it does not authorise a change. An implementation lead can route technical, contractual and clinical questions to the people able to answer them.
Review a change without pretending everything starts again
A processing change may allow some existing evidence to be reused while requiring other parts of the assessment to be revisited.
For example, a familiar interface may preserve training requirements for some tasks. A changed model may still require regression testing of clinically important output behaviour. New processing entities or locations may require information-governance work even when the note looks the same.
Document what remains applicable and why. The clinical model-change guide explains how to make that decision proportionate rather than treating every release as either trivial or a completely new service.
In applicable English NHS deployments, manufacturer and local clinical-risk responsibilities remain distinct under the clinical safety standards.
Registry inclusion does not settle the local decision
NHS England's ambient-scribing information describes a self-certified supplier registry, not an endorsement that removes local assurance.
That distinction should remain visible when a team assesses a partner route. A listed supplier, a product configuration and a locally approved use are not the same object.
The organisation should establish which evidence applies to the contracted service and which assumptions depend on the way it will be used. Existing procurement material can be useful without answering every new configuration question.
A deployment should not acquire an "NHS-approved" label merely because a related company appears in a national resource.
Tell users what changes and what does not
If the organisation adopts a different arrangement, communicate the practical consequences. Staff need to know when it applies, whether any feature behaves differently and where to report a concern.
Patient explanations should also reflect the actual service. Do not describe a new sovereign option to patients before confirming that it covers the processing in their consultation.
Equally, a change in infrastructure should not distract from reviewing the note or maintaining an ordinary documentation alternative. The patient-information article separates a verified infrastructure statement from those continuing responsibilities.
The next step is confirmation, not speculation
For an NHS clinician, the announcement is a reason to ask the local implementation lead a better question. For the lead, it is a reason to obtain a scoped account from the supplier relationship actually in place.
For a practice considering a new purchase, compare the available options without assuming that a direct Tandem deployment and an Accurx service share identical terms or feature access.
The practical significance of Sovereign Health will depend on whether it meets a requirement the organisation has and can be introduced through an understood, supported route. The existence of a partnership is the starting point for that enquiry, not its answer.
Frequently asked questions
Has every Accurx Scribe deployment moved to Sovereign Health?
That is not established by the announcement. The organisation should obtain confirmation for its own contract and operating configuration.
Is Accurx Scribe unrelated to Tandem?
No. Accurx's published partnership announcement describes Scribe as built on Tandem technology. That relationship does not make every product feature or deployment arrangement identical.
Who should an individual NHS user ask about a possible change?
Start with the local implementation or service lead, who can obtain the relevant contractual, technical and clinical information through the actual supplier route.
Use the twelve-question guide for a deployment-specific supplier discussion