AMBOSS's stated integration vision explicitly combines three distinct sources: its own curated knowledge base, external clinical guidelines, and hospital-specific local protocols. Bringing all three into a single answer sounds straightforward. Deciding, reliably and transparently, which one should win when they genuinely disagree is a considerably harder and more consequential product problem, worth examining directly.
Why local content matters as much as it does
Local, institution-specific guidance covers genuinely important, high-stakes ground that national guidance often cannot, and should not, try to specify in the same detail. Antimicrobial guidance, reflecting a specific hospital's own resistance patterns, is a clear example. Referral pathways, reflecting the actual structure and capacity of a specific local health system, differ meaningfully between institutions. Formulary restrictions, reflecting a specific hospital's own procurement and stocking decisions, directly shape what can actually be prescribed on site. Escalation policies, defining exactly when and to whom a deteriorating patient should be escalated, are inherently institution-specific. And discharge processes, reflecting local service structure and follow-up capacity, vary considerably between hospitals even within the same country.
Why combining local and national guidance is genuinely difficult
Several concrete problems complicate any attempt to combine these sources reliably. Local guidance may simply be outdated, not yet reflecting a more recent national update. Different hospitals may hold genuinely conflicting local policies on the same clinical question, meaning there is no single, universal "local" answer even in principle. National guidance may, in some circumstances, supersede local practice that has not yet caught up. And local documents, in many real institutions, notoriously lack consistent version control, making it genuinely difficult for any system, human or automated, to know with confidence which version of a given local protocol is actually current.
A proposed source hierarchy worth adopting
A defensible working hierarchy, applied consistently, might run: a time-critical local operational pathway where one genuinely applies to the specific situation, current national guidance where no time-critical local pathway overrides it, authoritative medicines information for prescribing-specific questions, and the strongest relevant scientific evidence where neither local nor national guidance has yet addressed the specific question at hand.
What the AI should display alongside any answer
Regardless of which specific source ultimately informs a given answer, several pieces of metadata should be visible to the clinician rather than hidden behind the final synthesised response: the source owner, identifying exactly which body or institution produced the guidance; its publication date; its review date, indicating how current it actually is; the jurisdiction or institution it applies to; and any known conflict with other guidance the system is aware of, rather than silently resolving that conflict without flagging it.
Comparing how different platforms currently approach this problem
AMBOSS's stated vision explicitly incorporates local protocols alongside its own knowledge base and selected guidelines, though the specific precedence logic between these sources when they conflict is not yet fully documented publicly. UpToDate's enterprise offering and ClinicalKey AI both operate primarily around expert-authored or curated national and international content, with local-protocol incorporation typically handled through separate institutional configuration rather than as a core product feature. And Medwise-style local-document search tools approach the problem from the opposite direction, starting with local institutional content and treating national guidance as a separate reference layer rather than the other way round.
Where iatroX is positioned on this question
iatroX offers a genuinely strong current national UK layer, built around NICE, CKS and SIGN. Compatibility with local institutional documents remains a potential future direction rather than a current feature, and this article makes no claim that iatroX currently ingests or reconciles local hospital protocols. What iatroX does not need to do is obscure the distinction between national and institutional guidance; that distinction, kept visible rather than blended away, is precisely the design principle this article argues every platform in this category should adopt.
A conclusion worth taking seriously
Ingesting documents, whether local protocols, national guidelines, or both, is technically the easy part of this problem. Establishing safe, transparent precedence between sources when they genuinely disagree, and maintaining reliable version management over time as any of them change, is the considerably harder and more important product problem, and it is where the real competitive and safety battle in this category is likely to actually be fought.