Pick a sample denial or type your own, then run it. Each step below shows the record exactly as that part of the system sees it. Every value here is synthetic, so please don't enter real patient details.
The webhook checks the API key and validates the payload. Patient data is still in the clear here.
Run a denial to see it arrive.
Name, date of birth and member ID become keyed-hash tokens. The same patient always gets the same token, and it can't be reversed without the secret.
Masked record appears here.
The provider reads the denial codes, picks a category and next action, and drafts an appeal using only tokens.
Only the tokenised letter is saved. A database leak would expose no names, dates of birth or member IDs.
Stored row appears here.
Tokens are swapped back for real values locally, so the billing team gets a letter ready to review and send.
Final appeal letter appears here.
Who acted, when, what they did and which record. Entries can only be appended, never edited or deleted.
| Time (UTC) | Who | Action | Record | Detail |
|---|---|---|---|---|
| No entries yet. | ||||