health · local-first tool
Track Health Record Requests and Follow-Ups
A request needs a destination, scope, sent date, and response status—not a guess about what a law guarantees.
Record the provider or plan contacted, record types requested, submission channel, user's follow-up date, and response status.
What changes the result: which record types you request, where you sent the request, and the date you choose to follow up.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Validate the date as a real YYYY-MM-DD calendar date, keep the user's status label, and order open items by their entered date. A past date is a comparison to the device's current local date; it is not a statutory or contractual deadline calculation.
Question to keep open: Should one broad request cover every record, or can a narrowly specified request make the exchange easier to track?
Boundary: HHS describes legal access rights and response timing with exceptions. This app does not compute a HIPAA deadline or determine whether a request is complete; confirm the process with the covered entity or HHS guidance.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.