Skip to main content

Under the Hood — March 2026

March was about making AI agents more capable and more connected. We expanded what agents can do — from booking appointments to managing ABHA profiles — while investing in the developer experience to make sure integrators can connect, authenticate, and build quickly.

Product highlights

  • ABHA login and profile management via MCP — AI agents can now handle full ABHA workflows (login, OTP verification, profile selection, card retrieval) during a conversation, no manual steps needed. View changelog
  • Vaccination and appointment reminder webhooks — New webhook endpoints for vaccination reminders, appointment reminders, and follow-up variants let integrations react to scheduling events in real time.
  • Follow-up appointment confirmation API — A new endpoint to programmatically confirm follow-up appointments, removing the need for manual intervention.
  • Ophthalmology data in prescription PDFs — Prescription PDFs now include pachymetry, Amsler grid, and contact lens examination tables, rounding out ophthalmology support across the platform.
  • IPD billing PDF generation — Clinics can now generate inpatient billing documents as structured PDFs with itemized charges and pricing summaries.

AI agent infrastructure

March saw sustained investment in the Eka MCP Server — the core interface between AI assistants and the Eka healthcare platform. We added five new tools this month: appointment rescheduling, patient benefits lookup, ABHA login and profile management, and doctor discovery with metadata forwarding. Each tool follows the authenticated remote MCP specification, so any compatible AI client can use them without custom integration work. Authentication got more flexible too. The MCP Server now supports email-based verification alongside mobile, and tools can prompt for credentials mid-conversation through elicitation — meaning the user never has to leave their AI client to authenticate. On the developer experience side, we restructured the MCP documentation into separate Remote and Local SDK guides, published the server on Smithery for easier discovery, and added comparison tables so developers can choose the right deployment model in seconds.

SDK and integration tooling

The EkaScribe Android SDK shipped Architecture V2 (v4.0.4) with Java support, session cancellation, and idempotent state management — a significant reliability improvement for integrators running the SDK in production. The JS SDK received error tracking improvements, header handling fixes, and ES6 build support. The Echo Agent Kit gained _meta field support and improved elicitation handling, aligning it with the latest MCP specification. The Pagify SDK cleaned up iframe lifecycle management to prevent lingering embedded views. On the mobile side, MedAssist on iOS now handles app backgrounding gracefully — sessions reconnect automatically — and error messages are surfaced clearly instead of failing silently. Suggestion chips, message bubbles, and file upload handling were all refined.

Documentation and developer experience

We published structured ABDM milestone guides (M1–M4) covering the full integration path from ABHA creation through health data exchange. The Doctor Profile API was extended with a salutation field. OPD slips now display price and patient attributes. The Medical Records Android SDK gained conditional visibility for record grid items, and the changelog itself was cleaned up (Gmail subscription links and GitHub repository links corrected).

What’s next

In April, we’re focused on expanding MCP tool coverage across the EMR, improving real-time event delivery for webhook consumers, and continuing to harden the authentication and session management layers across all SDKs.