The workspace that can't see the settlement number. BETA
Blocks valuation ranges, settlement figures, and advocacy language from the evaluator's workspace, neutrality enforced by design, not by policy.
Valuation data never loads into the session.
Settlement figures, demand amounts, reserve estimates, and advocacy-toned language are identified before a case file reaches the evaluator's screen, and withheld at the workspace layer rather than filtered after the fact.
Clinical and procedural content stays untouched.
The firewall targets valuation and advocacy content specifically. Diagnoses, treatment history, imaging, and procedural notes pass through in full, so the evaluator still sees everything relevant to forming a clinical opinion.
Works the same across legal, insurer, and TPA sources.
Whether a file arrives from a law firm, a carrier, or a third-party administrator, the same exclusion rules apply before the evaluator ever opens it. The referral source doesn't change the boundary.
Neutrality enforced by design, not by policy.
The Neutrality Firewall never exposes valuation data to the evaluator's session, even inadvertently. Settlement figures, demand amounts, and advocacy-toned framing are withheld at the workspace layer before a file is opened, not redacted after the fact.
Every exclusion is logged: what was filtered, when, and why, kept for administrator review. The boundary is verifiable, not just asserted, and it applies to every case the same way.
From intake to a clean workspace.
Three steps, every one logged, before the evaluator opens the file.
Documents are classified as they arrive, separating clinical and procedural content from valuation and advocacy material.
Settlement figures, demand amounts, reserve estimates, and advocacy-toned language are identified and held back from the evaluator's session.
The evaluator opens a workspace with the full clinical record and nothing else, with a complete exclusion log kept for admin review.
Built for the people who must stay neutral.
Same firewall, whoever commissions the exam.
Evaluators keep full clinical context without ever seeing what the case is worth.
For IME orgsA defensible, auditable boundary between claims handling and the exam itself.
For carriersOne neutral workspace standard across every evaluator in the network.
For TPAsFrequently asked questions.
It's a workspace boundary that blocks valuation ranges, settlement figures, demand amounts, and advocacy-toned language from ever loading into an IME evaluator's session, so clinical judgment stays separate from case value.
Settlement figures, demand amounts, reserve estimates, and language written to advocate for an outcome. Clinical history, treatment records, and imaging are not affected and remain fully visible.
Yes, in beta. The Neutrality Firewall is live and testable now; we're refining it hands-on with early customers, and if your use case is a good fit we'll work with you directly.
No. It changes what the evaluator can see while forming an opinion, not the report itself. Report drafting works exactly as it does today.
Yes. Every exclusion is logged with a timestamp and reason, and administrators can review the full exclusion log for any case.
Related to Neutrality Firewall.
Drafts the examiner's IME report from exam findings and the case record, ready for the examiner's own review.
Read moreSplits the case workspace into distinct evidence, work-product, valuation, IME-neutral, and audit views so privileged analysis never leaks into neutral opinion work.
Read moreRoutes the same file to two or three evaluators and shows exactly where their reads diverge, useful for high-value or disputed files.
Read moreGive your evaluators a workspace that can't see the number.
Join the beta and test the Neutrality Firewall on a file of your own, or book a demo to see the exclusion log in action. Handled under our BAA; never used to train a model.