Tally
Coding That Shows Its Working
Tally reads the signed encounter and recommends codes, modifiers and an E/M level, along with the passage of documentation that supports each one. A coder confirms or changes it before anything moves into billing.
The gap between what was done and what gets billed
Missed charges and under-coded encounters are not usually a knowledge problem. They are a volume problem: nobody has time to read every note closely enough to catch the procedure mentioned in the third paragraph.
Tally reads the signed documentation for every encounter and recommends the CPT and ICD-10 codes, the modifiers and the E/M level, then shows the specific documentation it relied on for each recommendation.
A coder or authorised staff member reviews, confirms or changes the recommendation, and the approved codes move into the billing workflow. The explanation matters as much as the recommendation: a suggestion you cannot audit is one you cannot defend.
Capabilities
What's included
Every encounter coded, and every recommendation explained
Code, modifier and E/M recommendations
CPT, ICD-10, applicable modifiers and the E/M level, recommended together rather than as separate passes.
Every recommendation is explained
Each suggestion points at the documentation that supports it, so a reviewer can accept it in seconds or reject it with a reason.
Missed charge detection
Procedures and services documented in the note but absent from the charge are surfaced before the claim is built.
Coder in the loop
Recommendations are proposals. A certified coder or authorised staff member approves, edits or rejects each one.
Why it matters
The outcomes practices actually measure
We are evaluated on the numbers that change in your operation, not on features shipped or tickets closed.
- Fewer coding errors and less rework
- Catching a specificity problem before submission costs a minute. Catching it after a denial costs a rework cycle and a timely-filing risk.
- Charges that reflect the work done
- Services documented but never charged are the quietest form of revenue loss, because nothing ever appears in a report about them.
- Faster coding throughput
- Coders review and confirm rather than reading every note from scratch, which is where the time actually goes.
- Audit-defensible decisions
- Because each recommendation cites its documentation, the reasoning behind a code is on the record rather than in somebody's memory.
How it works
What working with us looks like
- 1
Read the signed encounter
Tally works from signed clinical documentation only. Unsigned drafts are not a billing source.
- 2
Recommend and cite
CPT and ICD-10 codes, modifiers and an E/M level are recommended, each with the supporting documentation identified.
- 3
Human review
A coder or authorised staff member confirms or changes each recommendation. Nothing is auto-approved.
- 4
Move to billing
Approved codes move into the billing workflow, where Bulwark checks the resulting claim before submission.
Frequently paired with
FAQ
Tally, frequently asked questions questions
- Can Tally code an encounter without a human?
- No. Tally recommends. A coder or authorised staff member confirms or changes every recommendation before it enters the billing workflow.
- What does it need to work?
- Signed clinical documentation, a coding model appropriate to the specialty, and the claim fields that modifier recommendations depend on.
- Does it replace our coders?
- It changes what they spend time on. Reading every note end to end is the part that scales badly; reviewing a cited recommendation is the part that uses their expertise.
- How does it handle specialties with unusual rules?
- Coding models are configured per specialty. The 8-minute rule, device and cath lab rules, behavioural health time-based coding and similar specialty arithmetic are configured rather than inferred.
We're here to help
Ready to see what your revenue cycle could be doing?
Start wherever makes sense: a demo, a free assessment, or a straight conversation with someone who does this every day.