AMBOSS has set out a staged plan for bringing AI Mode directly into the electronic health record, and it is worth being precise about which parts of that plan are actually available today and which remain announced but not yet built, since conflating the two risks overstating what clinicians can currently rely on.
The three phases, stated accurately
Phase one is live: clinicians can open and ask AMBOSS questions without leaving the chart they are working in, but the tool does not yet read or incorporate any patient data as part of generating its answer. Phase two is coming soon, according to AMBOSS's own roadmap: AI Mode will use a patient's medical history, observations, laboratory results and current medicines to produce genuinely context-aware guidance specific to that patient. Phase three is still in development: structured suggestions, such as draft orders, notes or recommended next steps, may eventually be written back directly into the EHR for clinician review before being finalised.
Why this distinction matters more than it might seem
Opening a clinical search tool from within an EHR is a meaningful convenience improvement, but it is not the same thing as the tool actually analysing the patient's record. And analysing the record to produce a patient-specific recommendation is not the same thing as executing or documenting any action based on that recommendation. Each of these three represents a genuinely different level of capability, and a genuinely different level of risk, worth keeping clearly separate rather than treated as one continuous, already-arrived feature.
AMBOSS's proposed closed-loop workflow
The company's stated end-state vision runs through five steps: read the chart, connect the resulting patient context to trusted clinical knowledge, suggest appropriate clinical next steps, write structured output back into the record, and require clinician review and explicit action before anything becomes part of the formal patient record. This is a coherent, sensibly bounded vision, provided the final step, mandatory clinician review, remains genuinely non-negotiable as the system matures.
The potential benefits, taken seriously
Several genuine advantages follow if this vision is realised well. Less duplicate data entry, since a clinician would no longer need to manually re-enter information the chart already contains simply to ask a related clinical question. Reduced tab switching, keeping a clinician within a single working environment rather than juggling a separate reference tool alongside the EHR. Patient-specific rather than generic questions, allowing a query to be automatically informed by the actual patient in front of the clinician rather requiring that context to be typed out manually each time. And faster translation of evidence into documented action, shortening the gap between finding the right answer and it actually becoming part of the patient's care.
The unresolved questions worth naming directly
Several practical questions are not yet answered by the roadmap as currently described. Which specific record fields will actually be read, and which will remain outside the system's scope. How will incorrect or simply outdated chart data, a genuinely common feature of real clinical records, be handled once the system is reasoning from that data rather than simply displaying it. How will the system express genuine uncertainty, as distinct from confidently presenting a single recommendation. Will conflicting local and national guidance be surfaced explicitly to the clinician, or will the system silently resolve that conflict on its own. And which specific categories of suggestion will actually be eligible for write-back, given that a draft note carries different risk from a draft medication order.
Where iatroX sits today
iatroX currently functions as a low-friction UK clinical-knowledge layer, answering a clinician's question directly rather than reading or acting on a patient's chart. Deeper EHR integration of the kind AMBOSS is building towards remains a plausible future direction worth watching, not a feature iatroX currently offers, and this article makes no claim otherwise.