Medical Evidence & Contact Log
Most first applications are denied, and what decides what happens next is evidence somebody has to physically obtain: which provider, what record, when it was requested, whether it arrived, and what it shows. Claims are lost on gaps in that chain - a request nobody followed up, a specialist nobody listed - far more often than on the form. This keeps the chain, counts what is still outstanding, and counts down to the date printed on your own notice, which you enter yourself. It does not assume a deadline, because those differ by claim and stage and they change.
Your database
Fields
| Field | Type |
|---|---|
| Date of the record or event | date |
| What it is | select |
| Provider / clinic / office | text |
| Who you spoke to, and how to reach them | text |
| Where it has got to | select |
| Requested on | date |
| Received on | date |
| What it shows, in your own words | text |
| Claim / reference number | text |
| Notes | text |
Frequently asked
Where is this stored?
Only on this device, in your browser. Nothing is uploaded and there is no account. Export to CSV or JSON to back it up, hand it to an auditor, or move it to another machine.
Does it know my deadlines and required frequencies?
No, and that is deliberate. Inspection intervals, retention periods and review cadences are set by your standard, your jurisdiction, your certifier or your own procedure, and they change. This runs offline and cannot know if one changed last month, so it never asserts one. You enter the dates that apply to you and it does the arithmetic on those.
Why doesn't it just know my appeal deadline?
Because appeal windows differ by claim type and stage, have exceptions, and change - and a tool running offline that printed the wrong one would cost somebody their claim on the day it mattered most. Enter the date your notice gives you and this counts down to it.