Patient balances
Statements, plans, credits, and estimate timing.
A fair claim. Not a filed one. US 837, 835, 999, 277, 271, and 278 files. It does not submit, post, or refund.
Statements, plans, credits, and estimate timing.
Dental, anesthesia, equipment, lab, or telehealth, plus a coding sample.
EDI, remits, transfers, and credentialing blockers.
Scrub, modifiers, registration, eligibility, authorizations, rejections.
Fees against the Medicare file you provide, rates by volume, your measures.
Remittances, appeal drafts, contract pricing, and the balance to work first.
Setup is in English. The checks read files from the United States, Germany, France, Spain, Brazil, Italy, Japan, China, and Korea, including the encodings those systems write. The finding sentences stay in English. This is not a statement about any country's law.
Patient files stay on your machine. Setup is with you, over a shared screen. We do not take a copy. A business associate agreement is required only if you later ask us to hold a file. Masking a result is a design choice, not a HIPAA determination.
What the claim will need, from the registration export.
The 271 you exported. It does not log into a payer.
Whether the visit sits inside the authorization.
Good-faith estimates against your timing rule.
Charges against the encounter export.
What in an 837 would reject. It does not submit.
Your modifier rules. The code set is yours to load.
Each edit tied back to a claim.
Dental checks from your rules.
Anesthesia checks, including medical direction.
Equipment-claim checks from your rules.
Lab-claim checks from your rules.
Place of service and modifiers for a remote visit.
A sample you select. It does not choose a diagnosis.
Each 999 and 277 tied back to its claim.
The open accounts receivable you export.
An 835 matched to the deposit.
Denials by reason. A write-down is not called a denial.
A draft and a deadline. It does not send.
The line against your contract. A blank method prices nothing.
Credit balances and a refund draft. It does not refund.
The statement cycle, with the holds in your policy.
Payment plans against your own rules.
Your fees against the Medicare file you provide.
Contracted rates by volume, and the deadlines.
Payers scored from your own exports.
Expiry by payer. It does not enroll you.
A price file you already downloaded.
Your measures against the targets you set.
EDI, remits, and credentialing blockers. It does not go live.
Each one does one job, on your computer, from a file you export. There is no login to your bank, payer, carrier, or property system.
Run from a fresh download, 21 Nov 2026
On 21 Nov 2026 the repository was downloaded fresh and run on Node.js 22: all 865 unit tests and all 498 eval cases passed, and every one of the 30 demos ran with the network switched off. These are the product's own tests and eval cases, run on made-up files written by the same team as the checks. They show the rules do what they are written to do. This product has not yet had the final pass that 14 of the 17 products had (planted problems, clean files, one-change copies and public data), so there is no accuracy number to quote yet.
git clone https://github.com/fpavia111-creator/fairclaim-agents
cd fairclaim-agents
npm install
node packages/fairclaim-denial-worklist/bin/fairclaim-denial-worklist.js demo
Open source, MIT licence, on GitHub: fpavia111-creator/fairclaim-agents. Needs Node.js 20 or later. The demo runs on made-up files and needs no network and no setup. It writes its worklist to a new folder in your temporary files, inside a folder that still carries the product's earlier working name.
A Fairclaim tool reads the exported file on your own computer and returns a summary and a list of findings. Before that result leaves the computer, patient names, member IDs and record numbers are replaced with stable pseudonyms, birth dates are cut to the birth year, and addresses, phone numbers, e-mail addresses and Social Security numbers are removed, also inside free text. Strict mode also hides claim numbers, service days and ZIP codes. In the demo, none of the 64 made-up identifiers planted in the sample files appeared in the printed result. Report files written to your disk keep real names, because your staff work from them. Masking can be switched off, and that is recorded in the audit log. The result goes to whichever AI model your assistant uses; for patient data, use a local model or one covered by your own agreements. Masking is a design choice, not a HIPAA determination.
No count of planted problems found, no false-alarm rate on clean files, no one-change tests and no runs on public data have been recorded for Fairclaim. The readers for 837, 835, 999, 277CA, 271 and 278 files have been run on made-up files only, not on a customer's own file. Every setup starts by confirming the layout on your files. When the final pass is run, its numbers will be published here, including anything that fails.
We send the list of reports by name. You export them from the systems you already use; nothing is connected.
Over a shared screen: the checks are installed, your columns are matched, and your own rules and dates are set.
The checks run on your files. We go through the worklist with you, and every flagged row is a person's call.
You run them whenever you like. Support keeps the dated rules and the export layouts current.
A fixed scope and a fixed price, agreed before any work starts. Your files stay on your computer the whole time.
Written by the check itself on made-up files. Every person, business and number is invented.