Yes — for benefit rows. This is the part to understand before you turn writeback on.
When a full breakdown finishes and the patient's coverage is active, writeback clears every existing benefit row on that insurance plan and replaces them with the verified ones. The clear-out isn't selective. It removes rows your team typed in by hand, not just rows Stratus wrote on an earlier run.
And because benefits live on the plan rather than on the patient, this affects the plan record shared by every patient on it. Verifying one patient can change what your team sees for the whole family, and for other families on the same employer plan.
There's no preview and no undo.
Four things that are not overwritten
Your notes. Stratus writes inside its own clearly marked block in the plan note and in the appointment note, between a start and end marker. Text outside those markers is treated as yours and left alone. Each new verification refreshes what's inside the block, so it doesn't grow forever.
Insurance history. Only ever added to. We never delete a history entry, and if a date is already on file we skip it rather than write a duplicate.
Downgrade and substitution rules. Compared rather than wiped. We only touch codes the verification has an answer for. Substitution rules on any other code stay exactly as your team set them.
Everything outside insurance. Patient details, the schedule, treatment plans, claims and payments are never touched.
If coverage isn't active, nothing is cleared
When the patient comes back inactive or terminated, writeback skips the clear-out entirely. Your existing benefits are left as they are. Only the plan settings and the notes are refreshed, so you get the eligibility status without losing the benefit detail you already had.
Protecting specific entries
If there are procedure codes where your team's hand-entered figures are more reliable than a fresh verification, you can exclude those codes from writeback in the form builder — the icon beside each code toggles it between included and excluded.
For anything bigger than a few codes, email [email protected] before switching writeback on and we'll walk through it with you.