EVRESA CATN · Interactive build evidence for investors · October 2026
Less time on prior authorization. Faster care for patients.
CATN is built for doctors first. It prepares prior-authorization requests, catches missing documentation before submission and tracks every answer, so the practice spends less time on paperwork and patients start care sooner. It runs on RogueGuard, with RunGate at the last step, so no AI acts on a patient's case without a person's authority. Its dual ledger lets the practice prove what it sent, what was decided and what was paid.
Confidential · provided under NDA · not an offer of securities · no financial projectionsPatent pending
How to read this page: click any box to open its detail. The flow charts run on their own; pause them any time.
Live simulation · every action meets one gate · every outcome leaves a record
Status key:BuiltFunded firstFunded nextFuture, once fundedNot true yet
Proof of execution
What the code has already proven
Verified against the GitHub repositories, October 2026. Built and tested on synthetic data. Click a number to see what it means.
What is missing
Doctors lose the week. Patients lose the time.
Physician practices are the core market. The burden is measured, it delays care, and AI is now entering the workflow faster than the controls around it.
Source: AMA 2025 Prior Authorization Physician Survey, 1,000 practicing physicians, published May 2026. The two gauges for hours and weekly volume are drawn against a 20-hour and 100-request scale for illustration only.
Who it is built for
While AI agents move in, the controls around them are slipping
Wider market evidence that explains why an agent needs a registered identity, a stop button and proof of what it did.
One case, start to finish
Follow a prior authorization through CATN
Software recommends. A person decides. The core enforces and proves it. The marker moves through each stage; click any stage to stop it and read the detail.
Hover or click a stage to hold it open.
The engine under CATN
RogueGuard and RunGate
In a doctor's office, the AI agent is the software that prepares and submits requests for patients. RogueGuard makes sure it never acts without a person's authority, can be stopped everywhere at once, and leaves proof of both.
A stopped agent comes back only after a person reviews it.
Built and proven
Zero forbidden actions after a stop in 3,600 concurrent attempts.
Proven against a health-record server, a database and a payment system.
Works with the tools AI agents already run on and the major cloud key services.
A console showing every decision and every stop.
Where a system cannot be blocked directly, RogueGuard says so and watches it instead. RunGate ships inside CATN and RogueGuard, and the same engine can govern AI agents outside healthcare.
The differentiator
A dual ledger: proof that does not rely on anyone's word
Most prior-authorization tools keep one log of what they themselves did. That is self-attestation. EVRESA keeps the practice's signed record and checks it against the other side's own records. Click any box.
Built for the prior-authorization path and tested on synthetic data. Live connections follow pilot agreements.
What the dual ledger gives a practice
Where it meets CMS and HHS rules
The rules are setting the clock
Dates below are checked against CMS fact sheets. Click a date for what it requires and what CATN gives the practice.
Rule
What it requires
What it gives the practice
Status
CMS-0057-F
Decisions within 72 hours (expedited) and 7 calendar days (standard), from January 1, 2026
Every request's clock runs from the recorded submission; an overdue decision is flagged so the patient is not left waiting
Built
CMS-0057-F
A specific reason for every denial, from 2026
The stated reason is captured into the case, so staff can fix and resubmit or appeal quickly
Built
CMS-0057-F
Prior Authorization API (HL7 Da Vinci PAS) by January 1, 2027
Requests go electronically through the standard CMS names; every exchange is recorded
Built
HIPAA (HHS)
Minimum-necessary disclosure and an access trail
No patient data in receipts; disclosure only by a person; minimum-necessary export profiles next
Partly built
Why this is missing, and why it is investable
Five facts that make the case
Each step stands on a measured fact or on code that already runs. There are no financial projections on this page.
Why doctors will choose CATN
What a practice needs
Typical prior-authorization tool
CATN
Speeds up submission
Yes
Yes
Keeps a log of what happened
Its own log of what it did (self-attestation)
Practice's signed record, checked against the other side's own records
A person released every request
Not the design point
Yes: software recommends, a person decides
Can stop any AI agent at once
Not the design point
Yes: one person-approved stop, everywhere it acts
Proves the outcome independently
Not the design point
Yes: Evidence Passport, verifiable offline
Category-level comparison from the investor edition, not a claim about any one vendor. How we get paid: a subscription per practice, priced by request volume, not per seat. Pricing is validated with the pilot practices before it is published.
Who and what
The team, and what it builds
Click any box. The second view shows the chain of authority a case follows, from the practice's own sign-in to proof.
What the team has built and is building
Risk ledger
What the code has retired, and what the round funds
Capital removes risk. Each row is a question a buyer or investor asks, and where it stands. Click the bar to filter; click a row to open it.
Nine questions
What the round funds
Five milestones, each one retires a named risk
Milestones and what each one builds. Amounts are shared separately.
Deliberately not built this round
EHR write-back, advanced analytics and other industries wait until the pilots or real volume call for them.
Plain facts
What is not true yet, and how the software is checked
Not true yet
No live payer or EHR connection: everything runs on synthetic data and a synthetic payer.
No signed pilot agreements yet; signing design partners is the first milestone.
No independent security review yet; it is a funded, committed milestone.
No production deployment and no certification (HIPAA, SOC 2) is claimed.
RogueGuard has run against reference servers and sandboxes, not yet inside a customer's production systems.
How the software is built and checked
Every change is tested and recorded with its reasoning before it is merged.
Tests run automatically on every change, on two databases.
A case's proof can be verified offline by anyone, without trusting EVRESA.
An outside security assessment is a funded milestone, not an afterthought.
Team
JR
John Gray Rodriguez
Founder & CEO
25+ years building national multi-site networks, including HearUSA (289 locations) and Banfield Pet Hospital (Mars, 1,300+ leases). Led national market planning at Jackson Hewitt through its 2004 IPO; on the market-planning team behind Dunkin' Brands' 2011 IPO. UCF alumnus.
CR
Chris Rodriguez
CTO & Co-founder
25+ years of enterprise infrastructure at Pure Storage, Dell EMC and NetApp. Has led federal executive-branch infrastructure migrations under chain-of-custody requirements.
GF
Gil Feliciano
CMO & Co-founder
U.S. Navy veteran with 35+ years of marketing, including cross-border work across Latin America with government entities and large enterprises.
Intellectual property
Patent pending. Two U.S. provisional patent applications were filed in December 2025 on the human-authority architecture and a dual-layer ledger. Applications covering RogueGuard and RunGate are in preparation. Filing details are available under NDA.
Available for diligence
Live demonstration
A case from intake to verified proof, and an AI agent being stopped.