Chart writes
Review a proposed change before it saves
Last EHR pauses each write tool for a human decision. The approval card shows what the agent proposes; Approve sends that change to the FHIR backend, and Cancel saves nothing.
What the agent can propose
- add_note
- Propose a free-text clinical note. The approval shows the proposed diff beside cited and session-read resources, and flags a proposal that cites none.
- record_observation
- Propose a measurement. A recognized vital gains LOINC and UCUM coding from a pinned table; an unrecognized label stays honestly uncoded. The approval shows that body as a diff beside cited and session-read resources.
- record_superseding_observation
- Correct a wrong value without an update: the new entry is filed linked to the one it supersedes, and the approval card states that the earlier entry stays on the chart. The earlier row is listed with the other resources read before the proposal.
- create_task
- Propose a follow-up task, optionally with a due date. The approval shows the proposed diff beside cited and session-read resources, and flags a proposal that cites none.
These tools create Communication, Observation, or Task resources. They do not update or delete existing records. A correction creates a linked, superseding Observation; the earlier entry stays on the chart.
What happens when you approve
Ask “Record a heart rate of 72 bpm for Maria Garcia.” The agent first finds the patient, then prepares a measurement proposal. Review the patient, label, value, and unit on the card. Only an explicit approval runs the write.
The backend still checks the caller's permissions. On the authenticated Medplum path, an AccessPolicy can reject a write even after you approve it. Agent-created resources carry an AI-assistance label; deployments can also record Provenance.
Approval confirms your decision to save the proposal. It does not establish that the content is clinically correct. Chart reads also run without this checkpoint and, in external model modes, send context to the configured provider. Use synthetic data while evaluating this alpha software.
Use the same pattern in an MCP client
The MCP package exposes chart reads by default. Enable its write profile explicitly with LASTEHR_MCP_WRITES=proposal. Write tools are then available only to a client that supports the approval prompt. Each proposed action waits for a human decision.
The draft write protocol documents the proposal, decision, commit, and audit steps. Its conformance suite tests approval, denial, cancellation, and failure paths against a synthetic FHIR store.