Outstanding records, chased automatically.
Medical records request tracking keeps every outstanding record request moving: tiered follow-up escalation, configurable aging thresholds, and a full audit trail. Overdue requests climb the tiers and stay at the top of the queue until resolved — and received records land in the case file for review.
One boundary, stated plainly: it tracks and escalates the requests you send — it does not retrieve records from providers.
Tiered follow-up, on a schedule you set.
Each request carries its own escalation ladder: a first-tier reminder after a set number of days, a second-tier escalation to a supervisor or alternate contact, and a final tier that flags the request for formal action. No spreadsheet, no sticky notes, no request forgotten in a drawer.
Overdue never hides in the pile.
A due date per request, or a default aging threshold per provider type — when a request passes it, it gets flagged, climbs the tiers, and sits at the top of the queue until it is resolved or closed. When records do arrive, they land in the same case file, ready for review.
A paper trail for the paper chase.
Every event in a request's life is logged: when it was opened, each follow-up and escalation, every status change, and who touched it. When a court or an auditor asks how diligently a record was pursued, the answer is an export, not a reconstruction.
It tracks the chase. It doesn't fetch.
Medrecords AI is not a records-retrieval service and won't pretend to be one. Your team sends the requests and holds the authorizations; the platform makes sure every request is visible, escalated on schedule, and documented to an audit-grade standard — the same source-linked, legally defensible discipline as everything else on the platform.
See Audit Trail & Chain of CustodyHow it works.
Three steps, in the same workspace your case file already lives in.
Provider, what was requested, when, and a due date — or start from the gaps missing-records identification found.
Tiered reminders and overdue flags fire on your schedule; every event lands in the audit trail automatically.
Mark the request received; the new batch routes into supplemental record review, deduplicated against the file.
Who's been asking for it.
The teams that chase the most custodians, across the most files at once.
Records request tracking, answered.
No. Evidence Request Automation tracks and escalates the requests your team sends — it is not a records-retrieval service and will not contact providers or obtain records on your behalf. You send the requests; the platform makes sure none of them go quiet.
Each request carries a follow-up schedule you configure: a first-tier reminder after a set number of days, a second-tier escalation to a supervisor or alternate contact, and a final tier that flags the request for formal action. Every tier change is logged.
A due date you set per request, or a default aging threshold per provider type. When a request passes its threshold it is flagged overdue, moves up the escalation tiers, and surfaces at the top of the queue until it is resolved or closed.
Every event in the request's life: when it was logged, each follow-up and escalation, every status change, and who touched it. The trail is exportable, so you can show a court or an auditor exactly how diligently a record was pursued.
The new batch routes straight into supplemental record review, deduplicated against the pages already in the file, so it lands ready for review instead of sitting as a separate download to sort through by hand.
Available today
Finds the visits, providers, and date ranges that should exist but weren't produced.
ExploreAn immutable log of every ingest, access, edit, and export — exportable custody reports.
ExploreNew record batches arrive pre-deduplicated, summarized, and flagged where they matter.
ExploreStop chasing records by hand.
This workflow is planned, not generally available. Book a conversation to discuss the intended scope, safeguards, and whether roadmap access fits your team.