Every claims platform assumes it is printing a document for an insurance plan. Ministries taking administration in-house, or leaving a TPA built for insurance, find that out the first time a member document says “benefits,” “covered,” or “deductible.” So what is the document supposed to say instead? A health sharing ministry sends an explanation of sharing (EOS): the same job an explanation of benefits does, a line-by-line account of what was billed, what was eligible, what the community shared, and what the member owes, written in sharing language instead of insurance language.
Wording is an operating constraint here, not a style preference. It is also the first thing a ministry checks in any software demo.
Why a ministry doesn’t send an EOB
An explanation of benefits is the member-facing statement of an insurance claim decision. Its vocabulary assumes a contract of insurance: benefits, coverage, plan paid, denied.
A health sharing ministry presents itself differently. Members share eligible medical expenses with each other under published guidelines. A document that tells a member “your plan covered this claim” says something the ministry does not say anywhere else. We aren’t going to tell you how your ministry should word its notices; that is a question for your advisors. What we can say is that the claims system has to let you choose the words, and use them consistently.
What an explanation of sharing has to show
The EOS answers the same four questions a member asks about any medical bill. Your guidelines decide the exact fields, but a useful one carries these:
- What the provider billed, and what portion of that is eligible for sharing. The two numbers differ whenever pricing, a discount, or an exclusion has changed the amount.
- The shared amount, what the ministry’s community will share on that line.
- The member responsibility, the portion the member owes, whether from a sharing limit, an initial unshared amount, or an ineligible charge. The member responsibility amount is the number members call about, so it should be the easiest one on the page to find.
- A status for every line, so the member can see why each line landed where it did.
Per-line detail matters because a single claim often mixes outcomes. An office visit, a lab, and a cosmetic add-on can appear on one bill and each go a different way. A single total at the top tells the member nothing about which line to question.
A per-line status a member understands
The status on each line does most of the explaining. In Claimaro every line carries a status in your words, so a ministry can say “Accepted” and “Declined” where an insurer would say “approved” and “denied.” When a line is not shared, the member sees the reason with it. The column headings follow your wording too: the “Allowed” amount can read “Eligible,” and “Your responsibility” can read “Personal responsibility,” or whatever your guidelines use.
The same idea applies one level up, on the member’s plan page. Each benefit there can show as Sharable, Discount, Included, or Not sharable, or be hidden from the member view, with each word set in your own wording. That page answers “what does my membership share?” before a bill ever arrives, which cuts down the calls the EOS would otherwise generate.
What each word means is defined by your guidelines, so the software should show your definitions and not ours.
Where the words live: the whole system, not only the PDF
Fixing the PDF is the easy part. A ministry that gets an EOS right and then lets “your deductible” appear in a text message has not solved the problem. Insurance wording leaks in from several places:
- The member portal, where benefits, balances, and claim screens all carry labels.
- Decision notices, the short messages a member gets when a claim is decided.
- SMS and email templates, which are written once and then forgotten.
- Benefit and accumulator labels, such as “deductible” versus “initial unshared amount.”
The practical test in a demo: ask to see a claim decision from the member’s side across every channel, not only the PDF. Then change one term and watch where it changes. If the answer is “we’ll replace those after go-live,” the wording is a project, not a setting.
How the EOS reaches the member
Three delivery paths cover most ministries.
Portal PDF. The EOS is a PDF the member views and downloads in the portal. It is the record of the decision.
Email. A decision notice tells the member a claim has been decided.
Text message. Short and plain, a good fit for members who don’t live in an inbox. The same wording rules apply: a text that says “your claim was denied” is an insurance message even if the PDF behind it is correct.
Whatever the channel, the EOS should be a product of the decision itself, not a separate document someone assembles after the fact. If staff have to build it by hand, the numbers on it will eventually disagree with the numbers in the ledger.
Where Claimaro fits
Claimaro lets you build the explanation document, whether you call it an EOB or an EOS, with your own wording and branding, and members view and download it as a PDF in the portal. Claim decision notices go out by portal, email, and SMS (adjudication capabilities).
Terminology follows your model, sharing or insurance wording, across the platform. Line statuses, amount headings, and the benefit statuses on the member’s plan page (Sharable, Discount, Included, Not sharable, or hidden) are all set in your own words, and accumulators include sharing limits as well as deductible and out-of-pocket (benefit design). The healthshare enrollment software page covers the member-side flow. For where the claims platform sits among the other tools a ministry runs, see the health sharing ministry software stack.
If you want to see a claim decided and the EOS appear in the portal in your wording, book a 30-minute walkthrough.
Frequently asked questions
What is the difference between an EOS and an EOB?
An EOB explains how an insurance plan processed a claim. An EOS explains how a health sharing ministry handled the same bill: what was eligible, what was shared, and what the member owes. They do the same job with different vocabulary.
Does a health sharing ministry have to use the term “explanation of sharing”?
The term is a convention, not a rule we can point you to, and what a ministry must or must not say is a question for your advisors. The software should let you choose whatever name and wording your guidelines use.
What should an explanation of sharing include?
At a minimum: the billed amount, the eligible amount, the shared amount, the member responsibility, and a status on each line so the member knows why. Your guidelines decide any further fields.
Can the wording change in the portal and in text messages, not just on the PDF?
In Claimaro the terminology follows your model across the system, sharing or insurance wording, and decision notices go by portal, email, and SMS. During any evaluation, check the member’s view in every channel rather than only the document.
