Roadmap
What works today, and what comes next
Last EHR is an alpha agent layer over a FHIR backend. Use synthetic data while evaluating it. The current work improves chart reads, human approval, and the evidence that each integration works.
Available now
- Chart reads and approved writes
- The web agent and MCP package share four read tools: patient search, chart overview, filtered sections, and document text. Write tools propose notes, observations, linked corrections, and follow-up tasks. Each write needs human approval; a correction adds a new observation and leaves the original in place.
- MCP over stdio or HTTP
- MCP is read-only by default, with approved writes available by opt-in. Version 0.4.0 adds an optional HTTP transport with OAuth and a separate FHIR credential for each caller. Stdio remains the default. A disposable Keycloak and Medplum run verified real login, caller permissions, and scripted approval decisions on October 22, 2026.
- Five FHIR backend adapters
- Medplum is the supported authenticated path. The included HAPI stack runs locally without credentials. Firely Server, Aidbox, and Oystehr have passed the synthetic backend checks. These evaluation paths are for synthetic data; authentication and permissions remain the backend’s responsibility.
- Write controls and audit records
- Approved writes carry an AI assistance label. Operators can enable Provenance records, an audit trail for rejected proposals, and policy hooks that can block a write before review or commit. A policy never replaces the human decision.
- A local walkthrough and conformance suite
- The local HAPI walkthrough needs no account or model key. CI checks the browser approval flow, synthetic workflow evaluator, and write-protocol conformance suite against that stack. These checks verify the mechanics of reads and writes; they do not establish clinical accuracy.
Next
- Verify a deployed MCP service
- Repeat the checks with hosted Medplum and a public HTTPS MCP endpoint, then verify human approval in a chosen MCP host. Record the reviewer identity and deployment configuration.
- Extend terminology beyond vitals
- Measurement names currently resolve through a curated LOINC table. Add reviewed code mappings for problems, medications, and vaccines, plus explicit laboratory coding.
- Complete the remaining reference coverage
- Add reference-based fixtures and verification for Medication and PractitionerRole, the two remaining US Core resource types. The existing reference reader is the starting point.
- Make backend evidence easier to repeat
- Record the backend version, Last EHR revision, report, and retest date for each verified adapter so the checks can be repeated against the same setup.
- Test the write protocol independently
- The Approval-Gated Agent Writes on FHIR protocol is a v0.1 draft. Recruit another implementation and use the conformance suite to find gaps in the specification.
How to help
Small PRs are welcome. Start with a reproducible bug, a documentation correction, or an adapter test. Discuss changes to clinical tools before adding them.