University of Utah
“A practical bridge from automated decisions to evidence-backed correction.”
Built For The Teams That Get Asked, “Prove It.”
VisArch shows what proof is missing before a Medicare claim is submitted, so teams can fix gaps before the payer asks.
Utah GOEO
“Infrastructure for trust, auditability, and responsible deployment.”
C
Utah Department of Commerce
“A path toward proof standards for regulated automated decisions.”
The closed loop
Missing proof becomes a fixable gap.
Step 1
Find Gap
What proof is missing?
Step 2
Add Evidence
Get the missing evidence.
Step 3
Check Again
Did the new evidence close the gap?
Step 4
Submit
Advance only when ready.
Defensibility graph
Proof Becomes A Drag-And-Drop Control.
Step #1
Define Action
Start with the proposed action VisArch checks before submission.
Step #2
Add Proof
Connect the evidence and policy checks required to support the action.
Step #3
Route Based On Proof
Advance supported actions. Send missing or failed proof to correction or review.
proposed action
837I Submission
supporting proof
Evidence Sources
requirements
Policy Checks
decision path
Route Lock
next step
Submit or Review
Simulations
Prove the graph before claims go live.
A graph defines what proof is required. Simulations show whether that proof path works. Generate edge cases, replay historical claims, and test route changes before live submissions depend on the graph.
Graph Stress Test
Generate edge cases to find missing proof, weak policies, and broken routes before rollout.
Historical Replay
Run past claims through the graph to see recurring proof gaps, review load, and first-pass readiness.
What-If Scenario
Add, remove, or change policy checks to see how claim routing, proof gaps, and submission readiness would change.
Claim economics
Hospitals spend an estimated $18B a year fighting claims after submission. VisArch moves that work upstream.
Claims Tested
0
Claims evaluated before live submission.
Avoidable Work Found
0
Proof gaps surfaced before they became payer disputes.
Revenue Protected
$0.00M
Estimated dollars protected by fixing claims before submission.
Benefits
Keep the proof path visible after the graph is built.
VisArch keeps action, evidence, policy, route, and correction records connected so teams can see what changed before a claim moves forward.
Graph Record
Keep the action, fields, evidence, policy checks, routes, and goal in one visible proof map.
Proof Checks
Show whether the claim has the documentation, evidence, and policy support required to move.
What Changed
Compare the original and corrected claim so the team can see which proof gap closed.
Route Decision
Advance supported claims and send missing or failed proof to correction or review.
Evidence Sources
Connect attached, local, mirrored, or live evidence without changing the claim payload first.
Correction Queue
Point missing proof to the owner who can resolve it before the claim is submitted.
Ready before submission
See what proof is missing before claims go out.
Build a defensibility graph, find proof gaps, and see how VisArch helps your team move claims forward with more confidence and less rework.