Medplum Monthly Update - February 2026 | Medplum

February was a productive month for Medplum. We shipped four releases — v5.0.14, v5.0.15, v5.1.0, and v5.1.1, including a minor version bump reflecting the depth of new capabilities — with over 130 commits from 25+ contributors. The biggest themes this month were WebSocket subscription stability and performance improvements, AI-powered provider experiences, scheduling refinements, and revenue cycle tooling — all advancing our 2026 roadmap priorities.

Features

Provider App: AI-Powered Spaces and Chat

David Yanez

The Provider app's Spaces experience gained significant AI capabilities this month, advancing our AI roadmap initiative:

The Foomedical demo — a sample patient-facing experience — was also updated to showcase the latest chat experience.

AWS Lambda Streaming for Bots

David Yanez

Bots deployed on AWS Lambda can now stream responses back to callers in real time. This unlocks Server-Sent Events-style streaming from Lambda-hosted bots — a foundational capability for building AI scribes, copilots, and other latency-sensitive applications. This directly supports the AI roadmap initiative.

WebSocket Subscriptions: Scale and Observability

Derrick Farris

February saw a major investment in WebSocket subscriptions, improving performance, reliability, and operational visibility at scale — directly advancing the Enterprise Scale & Infrastructure roadmap priority:

Scheduling Enhancements

Noah Silas

Building on January's $find and $book foundation, scheduling received several refinements this month:

Revenue Cycle: Claim Submission and Eligibility

David Yanez

Advancing the Revenue Cycle & Billing roadmap initiative:

Pharmacy Components

Oleg Rocklin

New React components for patient preferred pharmacy selection are now available in @medplum/react. This supports e-prescribing workflows and the ePrescribe integration roadmap initiative.

Multiple Redis Support

Matt Long

Medplum server now supports multiple Redis instances, enabling more flexible infrastructure topologies including Redis Cluster deployments and failover configurations. This is an important step for enterprise-scale deployments that require high availability for caching and pub/sub. ( self-hosting guide)

Instance-Level Custom FHIR Operations

Rahul Agarwal

Developers can now define custom FHIR operations at the instance level with resource input — enabling more granular, resource-specific API extensions. Combined with updated bot operation documentation, this gives builders more control over custom workflow APIs. For self-hosters, this is particularly valuable: you can expose clinic- or organization-specific operations directly on your FHIR server without forking Medplum, keeping your customizations cleanly separated from the core platform.

Security and Authentication

Developer Experience

Documentation

February's documentation work was substantial, with a major restoration of SDK docs and expanded coverage of operations, subscriptions, and integrations.

Operations and API

Darren Eam

Subscriptions

Provider and Clinical

Infrastructure and Security

Blog

Bug Fixes

Clinical Data

Scheduling

Server and Authentication

Infrastructure

Releases

Looking Ahead

February's investments in WebSocket subscription performance and Lambda streaming set the stage for more capable real-time and AI-powered workflows in Q1. The scheduling enhancements continue to push toward a full self-scheduling experience, and the Candid claim submission proof-of-concept marks meaningful progress on revenue cycle automation.

Join us on Discord to share feedback or follow along on GitHub.