The next phase of medical AI may not be the standalone chatbot. It may be the API layer that powers search, retrieval, summarisation, and evidence access inside other products — EHR systems, ambient scribes, clinical documentation tools, and institutional knowledge bases.
Why Medical AI Is Moving Beyond Chat Interfaces
The first wave of clinical AI adoption was chatbot-shaped: a clinician opens a web app, types a question, reads an answer. This workflow is useful but limited. It requires context-switching from the clinical system. It sits outside the clinical documentation workflow. It creates a separate interaction that competes for attention rather than augmenting existing tools.
The second wave embeds clinical AI inside existing workflows. OpenEvidence embedded into Mount Sinai's Epic EHR. UpToDate integrated into Microsoft Dragon Copilot. Tandem Health's AI operating system embedded into Doctor Care Anywhere's virtual care platform. The AI answer surfaces where the clinician already works — not in a separate tab.
What DR.INFO's API Suggests About the Market
DR.INFO's API page describes an "Evidence First Search" API for healthcare — retrieving answers from sources such as guidelines, medical journals, and drug databases. Its organisation tier includes EHR/EMR connection, speech-to-speech, SSO, and collaboration features.
This positions DR.INFO not just as a consumer chatbot but as potential clinical information infrastructure — an evidence-retrieval layer that could sit inside other products. If an EHR vendor, ambient scribe, or clinical documentation tool wants to add cited evidence retrieval, they could potentially integrate DR.INFO's API rather than building their own retrieval system.
This is the infrastructure play. Instead of competing for individual clinician attention in a crowded chatbot market, DR.INFO could compete to become the evidence layer underneath other products — similar to UpToDate's strategy with the UpToDate Connect API and Microsoft partnership.
The Difference Between API Infrastructure and Clinician Workflow
API infrastructure and clinician-facing workflow tools solve different problems.
Infrastructure tools answer: "How can we embed cited evidence retrieval into our existing clinical system?" The buyer is a technology company, EHR vendor, or hospital IT department. The value is technical integration. The differentiator is API quality, source coverage, citation accuracy, and reliability.
Clinician workflow tools answer: "How can I find the right clinical information faster during my working day?" The buyer is an individual clinician or training programme. The value is daily usefulness. The differentiator is speed, citation visibility, local guideline relevance, and practical features like calculators and exam preparation.
Both categories matter. But they serve different customers with different evaluation criteria.
Why Hospitals May Want Embedded Evidence Search
Hospital procurement teams increasingly recognise that clinical AI tools need to integrate with existing institutional workflows — not create parallel workflows. Embedded evidence retrieval inside the EHR, ambient scribe, or clinical documentation system reduces context-switching and increases adoption.
DR.INFO's organisation tier and API represent an early attempt to serve this institutional demand. Medwise AI's NHS Trust deployments serve a similar market from a local-guideline-integration angle. UpToDate Connect serves it from the incumbent content-publisher angle.
Why Individual Clinicians Still Need Simple Front-End Tools
While infrastructure integration matters for institutions, individual clinicians need tools that work now — without waiting for hospital IT to deploy an API integration. A mobile-accessible, fast, cited clinical search tool with calculators and exam preparation is immediately useful today, regardless of what the hospital's EHR integration roadmap looks like.
iatroX's public focus is the clinician-facing workflow: ask, calculate, revise, and learn. Infrastructure matters — but clinicians adopt tools through daily usefulness, not through API documentation.
Try Ask iatroX — clinician-facing clinical search, calculators, and exam preparation →