Give Your Coding Agent a Head Start on Medplum
Put Medplum's decision guides to work in your coding agent. They help it ask the right questions about your healthcare workflow, explain the tradeoffs, and find a documented path to implementation. Pair them with our persistent rules file to carry Medplum's conventions into the next coding task.
Our expanded AI coding guidance shows how to connect these resources to your project:
Medplum Monthly Update - October 2026
If you will be at HLTH in November, email us at hello@medplum.com and we will find time to connect with the Medplum team.
Medplum v5 earned Drummond Validated FHIRplace Silver status for Coverage Requirements Discovery in both the provider and payer roles, determined October 1. It is the first external validation of the prior authorization work that has been running all year, and it comes with a new CMS-0057-F page laying out which payers the rule touches and when.
October brought 296 commits from 20 contributors, with thirteen patch releases, v5.2.1 through v5.2.13.
Scheduling grew a configuration workspace a practice admin can actually run its calendar from, recurring appointment series through $book and $hold, and blocked time. The Provider App gained draft lab orders and a claim submission path with its own guide. A Project can now be deactivated, archived, and restored.
All of this continues to drive forward our 2026 roadmap priorities.
PlumCon 2026 - Materials & Agenda
On September 3, 2026 Medplum hosted PlumCon 2026 in San Francisco. Thank you to everyone who attended, spoke, and shared demos!
Below you'll find slides and available recordings for each session from the agenda, followed by demos from the community. Continue the conversation in the PlumCon Discord channel.
Medplum Earns Drummond Validated FHIRplace Silver Status for CRD
Medplum v5 has earned Drummond Validated™ – FHIRplace Silver (CRD) status for both provider and payer roles in the Q3 2026 testing cycle. The validation recognizes confirmed interoperability with multiple partners for Coverage Requirements Discovery (CRD) in a structured, production-representative FHIR testing environment.
An EHR That Teaches: Building an AI-Powered Clinical Learning Environment with Medplum
Building an open-source, AI-enabled clinical learning environment with Medplum and PhenoML
Electronic health records were designed primarily to support patient care, documentation, and billing. But what would an EHR look like if we designed it specifically for teaching? We’ve been thinking and writing about this topic for years. That's the question we set out to explore with this project.
Medplum Monthly Update - September 2026
PlumCon 2026 happened on September 3 in San Francisco. Thank you to everyone who spoke, demoed, and came. It was the largest gathering of people building on Medplum yet, and the community demos are posted on the lineup page.
September brought 153 commits from 21 contributors, with six patch releases, v5.1.37 through v5.1.42.
Scheduling gained rescheduling, overbooking, either/or participant search, and a workspace for configuring visit types. A new Cron resource decouples a Bot's schedule from the Bot itself. The Provider App grew a full billing setup flow, and a long list of identity and session hardening landed on the server. Two new long-form posts went up: the Awell Panels case study and How Medplum thinks about FHIR.
All of this continues to drive forward our 2026 roadmap priorities.
Awell Panels: Worklists That Update Themselves
Awell builds care orchestration infrastructure, and on top of it Panels, a work surface where care teams define a patient population, configure how they work it, and trigger what happens next. Panels is population and workflow agnostic by design: intake, surgery prep, prescription refill, chronic care management and post-discharge follow-up each need to see different data and follow different steps.
At a national post-acute provider running 180+ inpatient facilities, post-discharge follow-up runs on Panels at roughly 250,000 discharges a year, with about 500 weekly users. A voice AI agent handles routine outreach; case manager assistants handle everyone the eligibility rules exclude. Both work the same panel. Panels did not exist before this project. It went from its first two hospitals to all 180 in nine months, on self-hosted Medplum. Guideway Care assembled the solution, implemented it, and ran the rollout.
How Medplum thinks about FHIR
Most folks, before encountering Medplum, think of FHIR in one of two ways:
As a read-mostly interface bolted onto a proprietary EHR. Epic, Oracle Health, and exchange profiles like Da Vinci Payer Exchange all use FHIR only at the boundary between systems. The real data lives in someone's proprietary tables; FHIR is the negotiated contract at the edge.
As a FHIR repository you publish into. HAPI, Aidbox, HealthLake, and the Azure or Google FHIR stores are often stood up alongside the operational datastore that actually serves the application — a landing zone for exchange, analytics, or compliance, rather than the system of record your app reads and writes on the hot path.
In both models, FHIR sits off to the side, and a separate database is doing the real work of running the application.
So when developers come to Medplum, they usually ask something along these lines:
- "How is the data handled and stored in the DB itself? How does that relate to FHIR?"
- "If I point a SQL explorer at the Postgres database when running Medplum locally, will I be able to see what's happening?"
- "Can I get direct access to the rows in the database when using your hosted service?"
These are all very reasonable questions for developers doing due diligence on Medplum, and part of the beauty of open source is that you can inspect our implementation directly. We also think these questions come from a particular understanding of the relationship between FHIR and an EHR — and this post is about how that relationship is different in Medplum.
Medplum Monthly Update - August 2026
PlumCon 2026 is this Thursday, September 3, in San Francisco. The agenda is posted. General registration has closed, but waitlist spots are available.
On August 1 we hosted the YC x Medplum Hackathon at the Y Combinator office in San Francisco, where 160+ hackers built on Medplum in a day. Read the recap.
It was a heavy month of shipping: 198 commits from 22 contributors, with nine patch releases, v5.1.28 through v5.1.36.
DICOM moved to Beta, scheduling got its own React package and a mountable booking workspace — the fastest path yet from empty project to a working calendar. Terminology got its 2026 refresh with multi-language display support, and externally issued JWTs can now authenticate against a specific project rather than the whole server.
All of this continues to drive forward our 2026 roadmap priorities.
Medplum Terminology Services Update - 2026
We've been hard at work making updates to our Terminology Services to update them for 2026, and are excited to share all the new features and data sets available! The latest UMLS 2026AA data set has been imported into Medplum's hosted environment, and is available for customers to use in their self-hosted clusters as well. In addition, we've made a number of improvements across the core terminology API endpoints to make everything faster and serve multilingual users.