About this resource
Who writes this, and how we keep it honest
Walk the lane. Claims in, remittance out — and this page is where we say who is behind the words, where the material comes from, and what we refuse to publish.
The intake facts
What this site is, and what it isn't
It's a reference. We explain how claims lifecycle, remittance data, payment integrity, and straight-through processing fit together in U.S. provider and payer operations. It isn't a payment processor, a clearinghouse, a portal operator, or a channel for buying anything. We don't take claims, route payments, or handle your account. If you need one of those, you need an operator, and we'll point you toward the workflow you're trying to solve rather than pretend to be the vendor.
Reading
Plain explanations of how a remittance moves — the claims lifecycle, the remittance file, the reconciliation step, the release to the provider — with the terms a working team actually uses.
Standing
Open
Not a vendor
We do not process payments, run a Zelis portal on anyone's behalf, or stand between a payer and a provider's remittance. Where a platform's own function belongs in the flow, we name the layer and stop there.
Scope
Read only
Platform pages
Entries about Zelis, Zeils Agent, the Zelis portal, and the support material around them describe what each layer does in the flow. They are descriptions, not scorecards built on data we did not verify ourselves.
Format
Description
Corrections
If a page gets a workflow detail wrong, we'd rather hear it than not. Corrections move up the queue, and a flagged page is re-read before anything else is added to it.
Channel
Contact
How the research works
Three steps before a sentence is written
Each topic page starts from public documentation — payer remittance guides, platform material, and the general operating literature around revenue-cycle work. We read the platform's own description of what it does and where it sits in the flow before we write a word about it. Where a fact is uncertain or hasn't been confirmed, we leave it out rather than hedge it into a sentence. You won't find numbers on this site that we can't point to a source for.
Source material
Read the payer's own documentation first
Payer remittance guides, published platform material, and the working literature revenue-cycle teams use day to day. If a source contradicts itself, the page says so rather than picking the more interesting version.
Starts from
Public documentation
Placement
Name the layer the tool occupies
A platform posts to a ledger, or it carries a remittance file, or it brokers connectivity between a payer and a provider. Those are different jobs, and the page describes the one the tool actually does.
Layer in flow
Described, not scored
Verification
If we can't source it, we leave it out
No hedged sentences. No approximate percentage wearing a decimal point. A number on this site is a number with a source behind it, or the sentence is rewritten without the number.
Editorial rule
Source or drop
- Shift change
-
Keeping pages current when payers update their remittance requirements
Healthcare payment workflows change as payers update their electronic remittance requirements and platforms update their feature sets. We revisit topic pages on a rolling basis and add a note when a page's content reflects a material change in how something works. If a page looks stale to you, that's useful information — send it in and it moves up the queue.
-
The conflict-of-interest question
A slip we print in the open
-
We write about platforms in a space where those platforms sell to the people reading this site. That's a real conflict and pretending otherwise would be dishonest. Our approach: we don't take positions on pricing, we don't claim a platform is the best, and we describe what each tool does rather than recommend a purchase. If a page ever appears on this site with a commercial relationship attached, it will say so plainly at the top of the page.
- We do not accept payment for a placement, a rank, or a recommendation.
- Platform pages describe function, not commercial preference.
- Any future commercial relationship is disclosed at the top of the page it touches.
- Current record
- No active commercial pages
- As published on this site today.
The operator's notes
Why we don't publish reviews with testimonials
We don't invent reviews, ratings, or quotes from customers. If we can't verify who said something and where, we don't print it. That means our platform pages read like descriptions of what each product does rather than a scorecard, and it means we'd rather say "this platform occupies this layer" than rank tools we haven't independently tested. It's a slower, plainer way to write about software, and it's the only one we're comfortable publishing.
Reviews Do you test a platform before writing about it? Open
No, and we say so on the page. What we do is read the platform's own documentation, place it in the flow, and describe its function. A reader looking for a hands-on assessment won't find a dressed-up version of one here — and if a page needs a claim we can't verify, it goes without the claim.
Field note
A platform page should be readable by someone who has never opened the product.
Zelis pages How do pages about Zelis and the Zelis portal get written? Open
Whenever we cover the Zelis portal, or question-and-answer material like zeils agent support topics, we start from the vendor's own published documentation and the payer-facing remittance guides that sit alongside it. Where a detail isn't stated plainly anywhere we can point to, we leave that detail out of the page rather than fill the gap with something approximate.
Field note
A page about a portal should teach the reader what they will see when they log in, not what a vendor wants them to hear.
Who reads Who is this written for? Open
The core audience is practice administrators, billing managers, and revenue-cycle analysts at U.S. provider organizations, plus the operations people inside larger health systems who own payment posting and reconciliation. We also write for people onboarding into a portal for the first time and trying to figure out what they're looking at. If you're outside those groups and find it useful, that's fine too.
Field note
Written at arm's length — a runbook, not a slogan sheet.
What we won't do What won't appear on this site? Open
We won't publish invented statistics, fabricated customer stories, or platform rankings we can't back up. We won't present this site as a payment processor or as affiliated with any platform. And we won't use a metaphor to avoid saying what a workflow actually does. If a sentence on this site could describe any product in any industry, it's a sentence we should have deleted.
Field note
Prose that fails the "like what?" test gets cut in review.
Reach us How do I send a correction or suggest a topic? Open
Send questions, corrections, and topic suggestions through the contact page. If something here is wrong, the correction is more valuable to us than the compliment. We read everything that comes in and reply to the ones with a specific question or a specific error. You can also write to [email protected] — the message goes to the same place.
Where to write
450 Serra Mall, Stanford, CA 94305, USA · Monday to Friday, 9:00 AM – 6:00 PM.
Continue reading
The standard
A resource is only as useful as the reader's ability to trust it. If a sentence on this site stops being true, it stops being on the site.
Reach us
- [email protected]
- Phone
- +1-650-723-2300
- Address
- 450 Serra Mall, Stanford, CA 94305, USA
- Hours
- Monday to Friday, 9:00 AM – 6:00 PM
Lane open · editorial resource for U.S. healthcare payment workflows
Zeils Agent