Coverage at the front door
Asked once, in plain language, and used in every match that follows.
Tesryn Lab · Care networks
Insurance-aware Intake
Ask about coverage at the start, so nobody is matched to someone they can't afford.
In the workshop For networks whose clients claim on insurance · 2026
In the workshop. Designed and agreed, not started. If you need it, it moves up the list.
01 — What it will be
Coverage is the question that decides whether a match survives the first phone call. This asks it at intake — what kind of coverage, which carrier — and uses it in matching, alongside which carriers a practitioner will direct-bill. Receipts come out with the fields insurers actually ask for.
The moment it will earn its keepSomeone with a plan that covers one kind of practitioner is matched, first time, to one who direct-bills their carrier.
What it proves we can do
02 — What it will do
Four things it will do.
Who direct-bills whom
Practitioners say which carriers they bill directly; matching respects it.
Receipts that get accepted
The fields insurers require, present the first time.
No policy data kept
Enough to match and to write a receipt, and nothing more.
03 — How it connects
What it shares with the rest of the Lab.
The same things we know how to do keep coming back in different industries. This is where this one sits: what it proves, and what else proves the same thing.
Matching a person can check Weights, hard requirements and capacity — arithmetic with its reasons attached, never a model's hunch. Also proved by Part Finder, Referral Engine, Referral Platform.
Only what's needed, deleted on request The least data that makes the thing work, with forgetting built in rather than promised. Also proved by Tesryn Signal, Referral Engine, Referral Platform.
Plain language, no training day One action per screen, words the user already uses, and errors that say what to do next. Also proved by Tesryn Signal, Reconstruction Research Studio, Part Finder, Referral Engine, Command Center, Tesryn Launch, Referral Platform.
The whole map — six sections, and everything that proves them.
04 — What it's held to
- No policy or claim data is stored.
- Not electronic claim submission — that needs a vendor agreement and a privacy review first.
What it isn't. Not built yet, and never a claims system.
05 — The recipe stays in the lab
We'll tell you what it will do. Not how it's built.
Yours would be your own build, on your systems, and you'd own it outright: code, documentation, no lock-in. What we bring to it is the practice — we've solved this shape of problem before, so you're not paying for the first attempt. The method stays ours. And if what you need isn't here at all, that's the usual case — it's how every skill on this page started.