The meaningful addition would be work completed beyond the existing task and document, not simply another way to create them. Heidi already documents task extraction, organisation, assignment and document generation. Whether the anticipated Heidi Work product adds external execution, richer coordination or a redesigned workspace remains unconfirmed before the 30 September 2026 reveal.
This comparison is pre-launch analysis dated 27 September 2026. It is published by iatroX and includes iatroX as an adjacent clinical-reference and learning option, not as a scribe or task-execution substitute. No Work functionality has been tested for this article.
Start with the product that already exists
Heidi's Tasks help article, dated 20 July 2026 and checked on 27 September, describes more than a list of suggested actions. It includes tasks extracted from notes, deadlines, a central view and document generation. Assignment to colleagues is documented for Practice and Enterprise plans.
That is the correct baseline for a comparison. Calling Work the first time Heidi recognises a follow-up or generates a referral would misrepresent established functionality. Likewise, a workspace showing unfinished actions across sessions would need assessment against the master task list that Heidi already describes.
A genuinely new release can still create value by reducing friction between existing functions. An improved interface need not introduce a completely new technical capability to be useful. The distinction is between an improvement in how work is organised and an expansion in the work the system is authorised and able to perform.
Follow one referral through four different jobs
Consider a fictional outpatient review. The clinician decides to refer the patient to another service and records that decision in the encounter. No real patient details are involved in this example, and it is not a claim about an observed Work workflow.
Capture is the first job. The note should represent what the clinician actually decided, including any condition that must be satisfied before proceeding. An intention to consider a referral after receiving further information is not the same instruction as a referral approved for immediate submission.
Organisation is the second job. The action needs an owner and an appropriate deadline. The task should remain visible even when the clinician moves to the next appointment. These functions are valuable without involving any external submission.
Preparation is the third job. The correct document and supporting information need to be assembled. A draft could save effort, but someone may still need to check the destination, approve the content and use a separate submission system.
Execution is the fourth job. An authorised operation is carried out, and its result is recorded. Even here, the endpoint needs precision: uploading a document, submitting a referral and receiving acceptance are distinct outcomes. Work would not have to automate every stage to be useful, but its description should identify where it stops.
Why the meaning of done matters
As documented in Heidi Tasks and checked on 27 September 2026, a document-generation task can be marked done automatically when its document is ready. That completion rule is coherent for a task whose purpose is to generate a document. It is not evidence that the document was sent or that another organisation accepted it.
The important procurement question is therefore not whether the product has a completion indicator. It is what event changes that indicator. A practice using tasks to organise drafting may reasonably regard a ready document as completion. A practice seeking referral tracking needs a different endpoint.
A future product might preserve both meanings through separate stages. Document preparation could finish while submission remains pending. This would avoid forcing users to choose between an overly broad completed label and an indefinitely open task. It is a proposed design distinction, not a description of Work's interface.
Documented baseline versus anticipated expansion
The following comparison reflects public documentation reviewed on 27 September 2026. The Work column deliberately distinguishes unconfirmed scope from a finding that a feature is absent.
| Job | Existing documented Heidi baseline | What would need establishing for Work |
|---|---|---|
| Capture an action | Tasks can be generated from an encounter | Whether recognition changes, and what triggers it |
| Organise unfinished work | A central task view and deadlines are documented | Any additional coordination across related workflows |
| Assign work | Colleague assignment is documented for eligible team plans | Who may delegate, approve and execute each new operation |
| Prepare a document | Tasks can generate documents | Whether preparation uses additional information or destinations |
| Perform an external operation | The task documentation does not establish a complete external referral workflow | The exact authorised operation and supported route |
| Confirm an outcome | A document task can finish when the document is ready | Whether external submission, receipt or acknowledgement is tracked |
The table is based on Heidi Tasks and the direction signalled by the Work-related waitlist. It is not a hands-on comparison or a complete catalogue of every function elsewhere in Heidi.
What would an existing subscriber gain?
For a clinician already satisfied with documentation, automatic preparation could matter more than another note template. For a practice with an effective task list but repeated manual transfer, an authorised submission step could be the meaningful addition. For a team whose difficulty is uncertainty about ownership, clearer coordination might matter most.
These are different purchasing problems. The appropriate trial should begin with the unresolved problem rather than a feature label. An existing subscriber should be able to identify what changes in their current workflow and what remains unchanged.
Entitlement is a separate question. The public material reviewed on 27 September did not establish whether Work will be bundled into existing plans, purchased separately or restricted to certain deployments. Existing Tasks entitlements cannot be used to infer new Work entitlements. iatroX's dedicated Work pricing article examines that uncertainty without treating current Heidi subscription prices as a Work quotation.
Test the handover, not just the new screen
A useful proposed demonstration would start with the existing workflow and ask the supplier to complete the same fictional referral through the anticipated new one. Record every manual step, every request for approval and the evidence supporting the final status.
Include a changed destination after the first draft. The system should make clear whether the previous approval still applies and whether any earlier submission occurred. Include a missing attachment and ask how the unresolved action reaches its owner. Neither condition should be counted as a product failure simply because work stops; stopping may be the correct response.
The evaluation should also preserve a fair alternative: the existing Scribe and Tasks workflow may remain sufficient. A new product is not automatically a better fit for a practice that already completes the relevant work reliably with little effort.
Geography can settle the immediate decision
On 27 September 2026, Heidi's waitlist excluded the UK and Europe. That makes any Work-specific purchasing recommendation for those markets premature, regardless of how attractive the demonstration appears. Existing Heidi services should be assessed separately rather than treated as withdrawn. The waitlist supplies that launch-specific limitation.
For a UK team, the practical exercise is to understand its current product and record questions for a later eligible release. For a team elsewhere, country access still needs explicit confirmation; being outside a stated exclusion does not establish that every integration or plan is supported.
Verdict by reader scenario
An existing user who needs reliable notes and organised drafting may already have the relevant functions in Scribe and Tasks. A team seeking externally completed actions should ask whether Work demonstrates those specific steps and their outcomes. A buyer chiefly seeking better clinical reference or professional learning is making a different decision.
For that last scenario, per iatroX product information, September 2026, free Ask-iatroX provides linked clinical sources, while Socratic Tutor supports question-based reasoning practice. Neither should be presented as an operational alternative to Work. The fair comparison is between solutions to the same problem, not every product that happens to use AI.
Frequently asked questions
How might Heidi Work differ from Heidi Scribe?
It may extend assistance beyond creating documentation towards supervised completion or coordination of subsequent work. As of 27 September 2026, the precise difference remains a hypothesis pending product documentation and demonstration.
Does Heidi already have a task manager?
Yes: its Tasks documentation describes extracted actions, deadlines, a central list, document generation and colleague assignment on eligible plans. Those existing functions should not be described as unconfirmed Work innovations.
Would existing Heidi users need another subscription?
The public sources reviewed on 27 September 2026 did not establish Work-specific subscription terms. A current Heidi plan should not be assumed to include the anticipated product.